Common reasons why App Push Notifications might be duplicated
Usually, duplicate notifications occur due to sending the same push data multiple times. If you see multiple notifications in the Campaign Reports with the same message, check your server code that API requests are not repeated with retries or other code errors.
If you are moving to iZooto and continue to send push notifications from the previous messaging provider, this can also cause duplicates and you should discontinue sending from the previous messaging system as and when you start sending pushes from iZooto.
Check to make sure you do not have another push notification plugin/ SDK in your app as it could be trying to parse the iZooto notification, showing it twice. Our Android SDKs prevent duplicate notification by checking the notification payload for iZooto specific data.
Android devices with two copies of the app installed on the device can also receive duplicate notifications. This could happen if you have a production and staging/dev app installed at the same time with different Android package names. This would result in two different tokens being generated resulting in two notifications.
You can long-press on each notification to ensure they are coming from the same app.
If there were 2 or more subscribed device records in our database with the same Push Token, then the device would get 2 different notifications and each could be tapped on. We have checks to help prevent this from happening but can happen if you try importing the same token multiple times.
Still having problems? We are here to help!!
Make sure you are using the latest version of the iZooto SDK and try to get a log from the device if you are able to reproduce it.
Include as much as you can of the following details and share with our support team to help us find your issue quicker:
- SDK Version
- App Version
- Device OS Version
- Device Make & Model
- Building on Mac or Windows
- Logs of the app starting and the problem point
- Any other libraries or plugins in your app
- Details on reproducing the problem
Duplicate notifications happen when:
You are subscribed to the website from different browsers on the same system. Subscriptions from different browsers (or different profiles in the case of Google Chrome) are considered separate and would each receive the sent notification resulting in duplicates.
If the same iZooto web push pixel is added to different websites/origins and you are subscribed to all of them. In this case, even if the notification is sent once, it would be delivered for all the websites/origins with the same pixel resulting in duplicates.
An origin is defined as: https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy.
Since web push subscriptions are tied to the user's browser profile and site origin, when you send a notification from iZooto, it will show a notification per origin the user is subscribed under.
To fix this on your browser, reset your browser data for each origin where the same iZooto pixel is added.
If you suspect this is an issue for multiple users, you will need to add a new website on the iZooto panel and use the new website's push pixel on the website.
Users will need to return to the site to get the subscription refreshed.
You can also get duplicate notifications on the web if you subscribe to the same site on multiple browsers and/or the same browser but different Browser Profiles. When you click on the notification, it should open the browser under the browser profile you are subscribed to. You can reset your browser data to stop it from showing on either or both.
Updated over 1 year ago