When sending messages using GCM, I keep getting the response 'MismatchSenderId' [duplicate] - google-cloud-messaging

Question

This question already has answers here:
Why do I get "MismatchSenderId" from GCM server side?
(11 answers)
Closed 7 years ago.
I'm implementing a push notification server with GCM. I send a post request with a sender ID (application key) that I got from Google API Console, and a registration ID that I got from the GCM service.
The posted JSON includes one registration ID. I always get the same response:
{
"multicast_id":8546528660791862014,
"success":0,
"failure":1,
"canonical_ids":0,
"results":[
{
"error":"MismatchSenderId"
}
]
}
What might be the problem? What am I doing wrong?

Answer 1

Please uninstall your Android app from the device and run the app again.
Now you will get a new registration Id. That may solve your MismatchSenderId problem in a specific case (Sometimes it happens If you change/refresh your API key, but still using the old registration key). In my case, I got the registration Id first for my device and then I changed my API Key (on Google GCM server) and then I got MismatchSenderId error. Finally, I uninstalled my Android app from the device and the problem got solved.

Answer 2

See the Stack Overflow post Why do I get "MismatchSenderId" from GCM server side?.
From the URL above:
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.
Some people are reporting issues using the "Key for Server Apps" type of keys, but having success using the Browser Key type instead. Personally, the Server Key type works for me, but try both, YMMV.

Answer 3

Log in to Google Cloud Console
See example in picture attached:

Answer 4

You should use "Project Number" (i.e. numeric ID) for Sender ID, not the "Project ID"

Answer 5

This error for sure because you specified a wrong SenderID when you register your device:
Here is a sample of register request (fiddler)
POST https://android.clients.google.com/c2dm/register3 HTTP/1.1 Host:
android.clients.google.com Connection: keep-alive Content-Length: 83
Authorization: AidLogin 51734556544354357:9087138434543543508
Content-Type: application/x-www-form-urlencoded User-Agent:
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/39.0.2171.99 Safari/537.36 Accept-Encoding: gzip,
deflate Accept-Language: en-US,en;q=0.8,ar;q=0.6,fr;q=0.4
app=gpYOURAppHereloin&device=5112132132137117&sender=YourApplicationIDHere
You can find your SenderID by below steps
Open the Google Developers Console.
a page appears that displays your project ID and project number. For example, Project Number: 67023432432. Copy down your project number and use it as the GCM sender ID.
more info:
Getting Started : http://developer.android.com/google/gcm/gs.html
Mismatched Sender error : http://developer.android.com/google/gcm/http.html#Mismatched_Sender

Answer 6

I was copying code from a tutorial but forgot to change the project number in the source code. It was generating an ID for the tutorial author's project rather than mine, so check that you change your source code on the Android app!

Answer 7

Generate an API key from the API Console. Use browser app key in backend and use the project id as the sender id in your client code.

Answer 8

I had the same problem, but I made a stupid stupid thing: I had multiple projects in google console and I generated the registration Id for a project number that belongs to a project and I tried to send notifications to a Api key that belongs to another project.
First step at this error is to check the project with that you work.

Answer 9

Note that if your Sender ID changes, Google Play Services's com.google.android.gms.gcm.GoogleCloudMessaging.register() method will keep returning the original registration id regardless of the new Sender(s) ID. You would need to invoke same class' unregister() method for Google Play Services to refresh and wipe out previous stale cached values.
See API info here: com.google.android.gms.gcm.GoogleCloudMessaging.register()
As an alternative, you can always delete app's data or uninstall-reinstall as noted in a previous answer but this is something far from acceptable in a production environment.
In case you have changed GCM settings and your Sender ID(s), apps must know that they need to unregister and register anew into GCM. One simple way to achieve this is pushing a new version to the Play Store and let users download the update and have this version do the work at its first execution, albeit this will not count apps that for some reason don´t get updated.
On top of that, if you are storing registration ids in preferences or a database, don´t forget to refresh its value when the app gets updated because updates could imply id regeneration and it could be the case that your code and not GCM is the one that is wrongly caching previous ids. Follow general guidelines here:
General client-side implementation guidelines

Answer 10

I have a similar problem when I was testing out the Google Sample code found here https://github.com/GoogleCloudPlatform/gradle-appengine-templates/tree/master/GcmEndpoints and What XYZ said really helped me resolve this issue.
I was able to send the messages to my phone from my google app engine API Explorer under the messaging.messagingEndpoint.sendMessage method however in the google app engine console logs, it always said MismatchSenderId. The error logged when clearly there was not supposed to be an error bugged me.
I was really confused and here is how I managed to resolve this:
Uninstall your android app from your phone.
Reinstall your android app and take note of the reg ID.
Go onto API explorer under Services > registration API v1 > registration.listDevices and list all your RegID for GCM.
Copy this list somewhere - to notepad.
Go onto API explorer under Services > registration API v1 > registration.unregister and unregister all the regID that does not match to the one used by your app.
Retry sending the message and this time it should work without the error being recorded in the google app engine console logs.

Answer 11

You need to check the source of your registration id, you can not use a C2DM registration id within a GCM message post. From Google's Doc :
C2DM and GCM are not interoperable. For example, you cannot post
notifications from GCM to C2DM registration IDs, nor can you use C2DM
registration IDs as GCM registration IDs. From your server-side
application, you must keep track of whether a registration ID is from
C2DM or GCM and use the proper endpoint.
As you transition from C2DM to GCM, your server needs to be aware of
whether a given registration ID contains an old C2DM sender or a new
GCM project number. This is the approach we recommend: have the new
app version (the one that uses GCM) send a bit along with the
registration ID. This bit tells your server that this registration ID
is for GCM. If you don't get the extra bit, you mark the registration
ID as C2DM. Once no more valid registration IDs are marked as C2DM,
you can complete the migration.
Another thing need to pay attention is the SENDER_ID, the format of SENDER_ID is the numeric one if you use InstanceID to get RegistrationID, like
InstanceID instanceID = InstanceID.getInstance(this);
String token = instanceID.getToken(SENDER_ID, GoogleCloudMessaging.INSTANCE_ID_SCOPE, null);
The SENDER_ID could not use the project name, please use https://developers.google.com/mobile/add to get the "Server API Key" and the
"Sender ID".