Push Notification Error - 400 Invalid Push Token

Question

Created Aug ’24

Replies 3

Boosts 0

Participants 2

We are using fcm to send push notifications. Recently we noticed some of our ios devices were not receiving push notifications, failing. By using the Push notification console we can see we are failing from APNS, with a 400 - Invalid Push Notification. Once this occurs we dont get push notifications on that device. We have tried re-logging in and re-installing the app. This does not work initially. However eventually they start working again after re-installing, usually after at least a day. { "code": 400, "message": "bad-request", "reason": "Invalid push token", "requestUuid": "ee04b0f1-c6aa-4b5e-87c0-7df754801d6f" }

Any ideas why the token is deemed invalid? Is there any way to get more details?

Boost

Answer 1

Engineer OP

Apple

Aug ’24

Invalid push Token is not a mysterious error. It basically means what it says, that the token is invalid. Either it is simply wrong, or you are using it in the wrong push environment. Development tokens cannot be used in Production environment, and so on.

You will want to start with finding out what tokens Firebase is using, and has there been a mistake when sending the assigned token to Firebase. So, it is better to start with them.

We have a pinned post on how to provide diagnostic information so we can check what might be the problem. Please read through the post If you need assistance debugging your push notification issues

and supply the requested detailed information for a notification request that was not received and we can take a look. A lot of the information there is going to be specific to APNs, and you may need to contact Firebase to obtain that information anyways, like the actual APNs token - and not the Firebase equivalent.

Argun Tekant /  DTS Engineer / Core Technologies

0

Answer 2

McGrea OP

Aug ’24

Thank you for the quick response. We did start with FCM and determined the issue is with the APNS token. We confirmed this by using the APNS token in the push notification console. A test notification can be sent when the token is working and fails when our fcm notification are not working. We get a 400 - Invalid Push Token Is it possible to look up using the RequestUuid": "ee04b0f1-c6aa-4b5e-87c0-7df754801d6f"

The mystery is why the tokens seem to work and then on a subsequent login the tokins begin to fail. At that poin t the device cannot get PN for a period of time.

0

Answer 3

Engineer OP

Apple

Aug ’24

The RequestUUid does not match any of our ids. If you are seeing the same issue using the Push Notification Console, the apns-id set for the request is what we need to look up the events to see what might be wrong. Also include the exact time you sent the push request (include Time Zone)

We need this failed push request to have been sent in the past few days.

Argun Tekant /  DTS Engineer / Core Technologies

0