These responses we're getting from APNs (iOS, macOS), FCM (Android, Chrome, Firefox) and Windows gateways when sending notifications there.
Most of the errors are not directly related with Pushwoosh rather the platform configuration or the gateway status.
All platforms
Success
A notification has been successfully accepted by the gateway and should be sent to the corresponding device.
Unregistered
There is no such a token found on the gateway's side. Most likely because the application has been removed from the device or reinstalled. In case of removing, the token becomes invalid on the side of the gateway, however we can obtain such info only as a gateway response when sending a notification.
If the user installs the app again, we got a new token and will be able to send notifications again. See HWID and Push token behavior in case of reinstalling the application article for more info.
Such responses are just indicating of app removing/reinstalled, so this is not an error actually, rather that lifecycle of devices. For more information about device lifecycle, refer to this article: Device Lifecycle in Pushwoosh.
iOS
Invalid Token / Bad Device Token
This error usually points to the mismatch between gateways, i.e., you were sending pushes to your development/sandbox build through the production gateway or vice versa. It could be possible that some of your users have another build installed on their devices.
See more details here: Invalid Token/BadDeviceToken error in iOS push report.
Connection failed
Generally, the "Connection failed" status points to some issues with your APNs certificates. Most likely, you are getting this error because your APNs certificate for this application has been revoked.
Please, renew your certificate using our guides: iOS configuration.
Device Token Not For Topic
The Apple Push Notification service (APNs) identifies a mismatch between the push notification token and the app’s topic (typically the App ID). This mismatch prevents notifications from being delivered to devices.
See this article for the more info: [iOS] Got the DeviceTokenNotForTopic error.
In short, this happens when:
- The token issued to a device is linked to one Apple App ID, but the push SSL certificate on the server is configured for a different App ID.
- The APNs service attempts to send a push notification, but the topic (App ID) doesn't match the token on the device, triggering the error.
This error may occur during incorrect configuration of certificates on Pushwoosh side or the application bundle.
In some cases it may arise only for small amount of devices which are testing or developers ones. Such devices are usually subject to frequent changes of certificates or different test/stage build reinstalling. Typically, after the automatic token update on the affected devices (or reinstalling the build), such an error should disappear. We follow all Apple recommendations and best practices, updating tokens periodically.
However, if you see drastically increasing rates of this error, especially after a certificate update on the Pushwoosh application configuration or after releasing a new build in the store, please double-check your configurations, certificates, and App ID.
Android, Chrome
Sender ID Mismatch
This is a response we receive directly from FCM when submitting notifications. Please make sure that you are using valid Sender ID from Firebase Console in your application and in Pushwoosh platform configuration.
Please, renew your credentials using our guide: Android Firebase configuration
Invalid Registration
It means that the push token we tried to send the message to isn't valid. We remove such tokens from our database. Also, it's worth checking whether you have enabled notifications from your app on the device.
Not Registered
This status means one of the following:
- The device was unsubscribed from notifications;
- The application was deleted from the device;
- The push tokens of the device has expired.
Internal Server Error
It means that FCM itself failed to deliver the message to the device with the particular push token.
Unauthorized
Please refer to the following article — Unauthorized errors in the reports
GCM Request Contains Invalid Parameters
InvalidParameters
error is a direct response from FCM gateway, and it indicates that a request with invalid parameters has been obtained from the specified number of devices. Please note that there is no detailed description of this message in Google's documentation.
It usually only occurs on just one or two devices, in most cases on testing devices. So it may be related to the code or build credentials.
Sometimes, "GCM invalid parameters" response is related to using an outdated version of Pushwoosh SDK or SDK was integrated incorrectly.
Firefox
Unknown Mozilla response code
This status means that you are using the old version of our SDK. Please note that Firefox changed the push token format in version 45. In order to successfully send notifications, you need to download our latest Web Push SDK and update your application:
https://github.com/Pushwoosh/web-push-notifications
Windows
Unregistered
"Unregistered" status means that the push notification channel for your application has expired. Please refer to the following link for more information: PushNotificationChannel Class.
Token for the wrong channel
This error points to incorrect configuration of the application.
- Please double-check whether the access token provided in the request matches the credentials of the app that requested the channel URI.
- Please ensure that your package name in your app's manifest matches the cloud service credentials given to your app in the Dashboard.
Comments
0 comments
Article is closed for comments.