This error usually points to the mismatch between gateways, i.e you were sending pushes to your development/sandbox build through production gateway or vice versa. It could be possible that some of your users have another build installed on their devices.
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 Guide.
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.
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.
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.
It means that FCM itself failed to deliver the message to the device with particular push token.
Please refer to the following article - https://help.pushwoosh.com/hc/en-us/articles/360000340443-I-suddenly-started-getting-Unauthorized-errors-in-the-reports
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:
"Unregistered" status means that the push notification channel for your application has expired. Please refer to the following link for more information:
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.