Why do I get MismatchSenderId from GCM server side

Question

I m trying to create a push service for my Android app  and I follow Google GCM s documentation and example for this matter   I can register unregister my Android app  From my server side  I can see that I have one subscription registered  but when I try to send a message from server to my Android app I always get following error      Error sending message to device  0  MismatchSenderId   For my Android app  I use SENDER ID   200000000001   And for my server side as Google says I use API KEY   AIzxxxxxxxxxxxxxxxxXxxXxxXxxxXXXXXxxxxs  I followed this document       http   developer android com guide google gcm demo html   I ve enabled GCM in my Google API panel too  yet I ll get that annoying error message   How can I fix this problem

User · Answer

Use sender ID  amp  API Key generated here  http   developers google com instead  browse for Google Cloud Messaging first and follow the instruction

User · Answer

Your android app needs to correct 12-digit number id  aka GCM Project Number   If this 12-digit number is incorrect  then you will also get this error   This 12-digit number is found in your Google Play Console under your specific app   Service  amp  API  -   LINKED SENDER IDS

User · Answer

With the deprecation of GCM and removal of its APIs  it appears that you could see MismatchSenderId if you try to use GCM after May 29  2019  See the Google GCM and FCM FAQ for more details

User · Answer

If use for native Android  check your AndroidMaifest xml file    lt meta-data         android name  onesignal google project number          android value  str 1234567890    gt       lt  --             its is correct  -- gt    instead      lt meta-data         android name  onesignal google project number          android value   string google project number    gt    Hope it helps

User · Answer

I encountered the same issue recently and I tried different values for  gcm sender id  based on the project ID  However  the  gcm sender id  value must be set to the  Project Number    You can find this value under  Menu   IAM  amp  Admin   Settings   See screenshot  GCM Project Number

User · Answer

This happens when the  Server key and Sender ID parameters HTTP request do not match each other  Basically both server ID and Server key must belong to the same firebase project  Please refer to the below image  In case of mixing these parameters from deferent Firebase projects will cause error MismatchSenderId

User · Answer

Check google-services json file in app folder of your Android project  Generate a new one from Firebase console if you are unsure  I got this error in two cases    I used a test Firebase project with test application  that contained right google-services json file   Then I tried to send push notification to another application and got this error    error    MismatchSenderId     I understood that the second application was bound to another Firebase project with different google-services json  Because server keys are different  the request should be rewritten  I changed google-services json in the application  because I wanted to replace test Firebase project with an actual  I generated right google-services json file  changed request  but kept receiving this error  On the next day it fixed itself  I suspect Firebase doesn t update synchronously    To get a server key for the request  open https   console firebase google com and select an appropriate project     Then paste it in the request

User · Answer

Please run below script in your terminal  curl -X POST   -H  Authorization  key   write here api key    -H  Content-Type  application json    -d      registration ids       write here reg id generated by gcm       data       message    Manual push notification from Rajkumar      priority    high       https   android googleapis com gcm send   it will give the message if it is succeeded or failed

User · Answer

Did your server use the new registration ID returned by the GCM server to your app  I had this problem  if trying to send a message to registration IDs that are given out by the old C2DM server   And also double check the Sender ID and API KEY  they must match or else you will get that MismatchSenderId error  In the Google API Console  look at the URL of your project   https   code google com apis console  project xxxxxxxxxxx   The xxxxxxxxx is the project ID  which is the sender ID   And make sure the API Key belongs to  Key for server apps  with IP locking

User · Answer

InstanceID getInstance getApplicationContext    getToken authorizedEntity scope    authorizedEntity is the project number of the server

User · Answer

Mismatch happens when you don t use the numeric ID  Project ID IS NOT SENDER ID   It took me 9 hours to figure this out  For all the confusion created by google  check the following link to get numeric id    https   console cloud google com  instead of  https   console developers google com  Hope it helps    Update - Things have changed again  Now the sender id is with firebase   Go to https   console firebase google com and select your project  Under settings -  cloud messaging  you can find the sender id   And it works

[android] Why do I get "MismatchSenderId" from GCM server side?

Examples related to android

Examples related to push-notification

Examples related to google-cloud-messaging