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

Answer 1

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 2

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 3

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".

Answer 4

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 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

1. Open the Google Developers Console.
2. 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