Skip to main content
All CollectionsPush notificationsAndroid
How to fix a mismatch between your push tokens and your Sender ID?
How to fix a mismatch between your push tokens and your Sender ID?

What to do if you notice the following error : "This push token was registered with a Sender ID that doesn't match this authorization key".

Claire avatar
Written by Claire
Updated over a week ago

Push tokens are systematically attached to a Google Cloud Messaging (GCM) or Firebase Cloud Messaging (FCM) project.

Each project has two IDs:

  • A sender ID: set in the code of your app. Android Studio uses automatically the Sender ID of your Firebase Project. If you are still using GCM, you have probably set manually the sender ID in the code of your app. The sender ID identifies your app to Firebase Cloud Messaging when it asks for a token.

  • An authorisation key (or server key): Set in Batch's dashboard settings > Push settings. It allows our servers to push the tokens generated for your Firebase project.

You will find more information on that part here: Finding your server key 

Batch cannot push a token that hasn't been generated for the authorisation key used on your dashboard.

If you are seeing that error, then you probably:

  • Switched to FCM without migrating your existing GCM project. Tokens are now generated for a project that is not the one you were using in the past, and that doesn't match the authorisation key set on Batch's dashboard.

  • Changed the sender ID by mistake.

In order to fix the issue you can either:

  1. Migrate your old GCM project to Firebase, use it in Android Studio and send an updated version of your app to the Play Store.

  2. Or stick with the new project and add an additional Authorisation key on Batch's dashboard (in Settings > Push settings).

This article belongs to Batch's FAQ. Need more help? Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on and our blog.

Did this answer your question?