Troubleshoot Common Push Errors

Push Notifications can fail for various reasons- the token might have expired or the push message may have been too large for the Push service to process, and so on. Here are the most frequently occurring errors and their reasons.

Error or Alternative Error Description

Unregistered

Also known as:

  • Gone
  • Not Found

An existing registration token may cease to be valid in several scenarios, including:

  • If the registration token expires
  • If the client app is updated but the new version is not configured to receive messages.
  • The device is inactive.

Sender temporarily

Also known as:

  • unavailable
  • Internal Error
  • Internal Server Error from FCM Service
  • Temporary Error from FCM Service
  • The request timed out
  • Unknown server error

Either the Sender server experienced an internal error while trying to process the request, or it is temporarily unavailable.

Authorization Error

Also known as:

  • Bad Authorization
  • Forbidden

The Authentication Key for APNS or Web Push is invalid/expired. Please check your push Authorization setup.

Invalid Vapid Details

Vapid keys generated for Web push are wrong/invalid. Please check Web SDK integration or raise support ticket.

 

 

Was this article helpful?
0 out of 0 found this helpful

How can we improve this article?