FCM getting MismatchSenderId

Question

I have an application that uses Google FCM for sending push notifications   When i send a push notification to a group of users  i get a response of MismatchSenderId for some of them  Even though  all users have the exact same application  How can some of the users get a success response and others get a MismatchSenderId   I have researched a lot and made sure I have added all prerequisites that FCM needs   Any suggestions   EDIT   Sample response     multicast id  5340432438815499122  success  0  failure  1  canonical ids  0  results     error   MismatchSenderId       EDIT 2   Here is the server side sending code  PHP     fields   array      to    gt   token     data    gt   data      headers   array      Authorization  key AIza                                Content-Type  application json       ch   curl init    curl setopt   ch CURLOPT URL   https   fcm googleapis com fcm send     curl setopt   ch CURLOPT POST  true    curl setopt   ch CURLOPT HTTPHEADER   headers    curl setopt   ch CURLOPT RETURNTRANSFER  true    curl setopt   ch CURLOPT SSL VERIFYPEER  true    curl setopt   ch CURLOPT POSTFIELDS  json encode  fields     curl exec   ch    curl close   ch      UPDATE   It seems that the issue has been resolved with the SDK updates  I am using now the latest com google firebase firebase-messaging 9 6 1  I don t get  MismatchSenderId  anymore

User · Answer

I had big trouble figuring out why I was getting a "MismatchSenderId" status. I added the gms dependency in the root build.gradle but my error was actually not applying the gms plugin in the app build.gradle.

If you have don't have this line in the app build.gradle, this could be the reason why the notification are not working: apply plugin: 'com.google.gms.google-services'

User · Answer

I have noticed that when a device id is created in GCM you cannot send push messages through FCM using the new server key  you have to use the old API-key

User · Answer

Firebase has upgraded their server keys to new version  Use new keys instead of old one   go to settings- gt project settings- gt cloud messaging tab

User · Answer

I was trying to send notification using the fcm api  quot https   fcm googleapis com fcm send quot  from postman  Server key was ok and token was pasted fine but was still getting error  quot MismatchSenderId quot   Then introduced the follwoing dependency in the gradle file on android side  implementation platform  com google firebase firebase-bom 25 12 0     and it started receiving notifications on the device

User · Answer

Note  I had truncated the first part of the FCM token  before    and the error was MismatchSenderId  Fixed my script and now everything works fine

User · Answer

I had the same error while trying to send push notificaion  Get the updated google-services json file and replaced with it  Worked for me

User · Answer

In my case  I just was mistaking about project credentials  using google-services json from one project  and server key from another

User · Answer

I had the same problem  and I fixed it like this    Go to your google fcm console Select your app In the left side menu find settings icon  standard wheel  Click on it and after click on project settings Now copy your server key and paste it in php   Voila

User · Answer

In my case it was very simple  I was pulling the wrong registrationId from the database  After I pulled the correct Id  it worked

User · Answer

Updating firebase initialization works for me     lt script src  https   www gstatic com firebasejs 4 6 2 firebase js  gt  lt  script gt    lt script gt       Initialize Firebase      TODO  Replace with your project s customized code snippet   var config         apiKey    lt API KEY gt        authDomain    lt PROJECT ID gt  firebaseapp com       databaseURL   https    lt DATABASE NAME gt  firebaseio com       storageBucket    lt BUCKET gt  appspot com       messagingSenderId    lt SENDER ID gt           firebase initializeApp config    lt  script gt

User · Answer

your probably doing whwat i was doing  GCM token is not the same as FCM anymore  check if your pulling the GCM token ID instead of FCM  just override FirebaseInstanceIdService  amp  ensure your getting the right ID   i thought at one point they were the same but now there not  i logged a test and saw   after you do that also update google-services json like others say as a safety

User · Answer

I wasted days on this     In my case  I followed this blog to use Postman and get the mismatchsenderid error   Previously  I was getting messaging mismatched-credential  and people reported that their client app used multiple projects     However  for me  I have one-to-one  a web app and a project   BUT  I host all apps via ng serve on default port 4200   So regardless of what project   app pair I was developing on  I would always get the same token from my client web app using AngularFireMessaging requestToken - this token was always the token created on my first ever run of a firebase app in development   As a work around  I start different apps   projects on different ports and get proper tokens for respective projects

User · Answer

As per response  MismatchSenderId   this is a mismatch between FireBase and your local  google-services json   you have to make sure that both manifests matches  In FireBase console you go to  YourProject   Project OverView   Cloud Messaging  you ll see the  SenderID  which MUST match with the  google-services json  in your Android project     Best thing you can do is download the final json file from  General  tab and place it in your project

User · Answer

My problem was solved by entering the correct key as shown below  Copy Server key like this picture  And then copy this code in post man like this picture  and Body is row like this picture  NOTE   You must add key  before Server key in header Make sure you enter the header keys correctly  Authorization    quot key     quot  and ContentType    quot application json quot   You have sent the request to the correct address  https   fcm googleapis com fcm send and Post method

User · Answer

You will have a server key something like this AIzaSyDiTEVq4Li1pj7IyraRlyRU9adc-49-KVY available in the Settings section of firebase console  console firebase google com project project-XXXXXXXXXXXXX settings cloudmessaging   Specify the correct key with your code and try again

User · Answer

For eliminate this error for mismatch sender Id In fcm    multicast id  7751536172966571167  success  0  failure  1  canonical ids  0  results     error   MismatchSenderId       there is error occured     So we required first  In FCM  register Application e g MyDemoApplication After that FCM will generate server key i e AIzaSyB9krC8mLHzO TtECb5qg7NDZPxeG03jHU and sender Id i e 346252831806 these format like these  After In Android Studio  our project is connect to these FCM created project i e MyDemoApplication And most important step is there required to device token or registration id  These token must created in Android Studio    After that using Sender Id and API key in web API project u will be definitely getting notification

User · Answer

I spent hours on this and finally figured it out  This problem happens if service account your sender application is using differs from the service account your receiver is using  You can find out your receiver service account via Firebase - gt  Project Overview - gt  Project Settings - gt  Service Accounts and generate a new key and use that key when you are initializing your FirebaseApp in the sender  FileInputStream serviceAccount   new FileInputStream  quot YOUR PATH TO GENERATED KEY json quot    GoogleCredentials googleCredentials   GoogleCredentials fromStream serviceAccount   FirebaseOptions options   new FirebaseOptions Builder   setCredentials googleCredentials  build    firebaseApp    FirebaseApp initializeApp options    This initialization need to be done once before you send push notifications  In my case  I had done everything correctly and I still had this problem  I had made some changes in the  quot google-services json quot  used in the receiver app and I noticed AndroidStudio was not using my new file  The solution was so simple  AndroidStudio - gt  Build - gt  Clean Project and Build - gt  Rebuild Project

User · Answer

THIS WORKED FOR ME    CHECK WHICH FIREBASE PROJECT YOUR CURRENT ANDROID PROJECT IS LINKED TO AND USE  Server Key FROM THAT PROJECT    I was using Server key from a different firebase project say Project 2   I used the same server key as linked with my android project Say Project 1  and it worked  In my experience  using one firebase app for one entire android project seemed to fix the problem

User · Answer

I also getting the same error  i have copied the api key and change into google services json  after that it workig for me   api key                          current key                                               try this

User · Answer

We spent hours and hours to resolve this issue  What we found that token was being generated using different FCM account settings  google-services json  and notification was being set using different FCM account  When we synced both it worked like a charm

User · Answer

Make sure you remove all the Parse code from your app  libraries  receivers in AndroidManifest  etc   I found that intermittently push notifications were not working  From my observations  it would work on fresh installs but not app updates from the play store    I believe something internal to Parse was conflicting with FCM  Parse uses GCM  so I m guessing it had to do with using GCM and FCM simultaneously   As soon as I ripped out all the Parse receivers and libraries  things worked great

User · Answer

For me the problem was that I was using the phonegap-plugin-push in cordova  testing the app with the phonegap app   The problem with this is that for some reason with this plugin  the phonegap app intercepts it and returns a dummy registration key  no matter what sender ID you have    So to make it work  as long as you have all your keys right  is to test your program some other way  with an emulator  or android emulation via usb  And your keys will match   Hopefully this saves someone some time

User · Answer

Actually there are many reasons for this issue  Mine was because of Invalid token passed  I was passing same token generated from one app and using same token in another app  Once token updated   it work for me

User · Answer

check gcm sender id in manifest json  If mismatch - correct  but you need make new subscribers for new sender Id  Exists subscribers break

User · Answer

I found that the senderId is different from the project number in the FCM console so I re-downloaded google-services json and everything works fine

User · Answer

I cross verified all the credentials  Added new server key and deleted old one  Downloaded google-services json again   Nothing solved the issue Then I just clean the project and then rebuild the project After that it s working fine

User · Answer

I had the same issue in my react-native - node js project  I wanted to send notifications in android  Everything was set-up and working fine  i e  I was able to send notifications from node js and receive notifications on android device   After a few days  I had to use a different firebase account  so I changed the google-services json file in my project s android app folder and rebuilt the project  But  when I tried sending notification from my server once again  I got an error -                  errorInfo        code   messaging mismatched-credential       message   SenderId mismatch         codePrefix   messaging     Solution  the XML file at the location - app build generated res google-services  build type  values values xml was not getting automatically updated according to new google-services json  It still consisted of old values from my previous google-services json file  I had to change values xml file manually  This is how app build generated res google-services  build type  values values xml file look  You need to change it manually if it does not get updated automatically according to google-services json -  lt  xml version  quot 1 0 quot  encoding  quot utf-8 quot   gt   lt resources gt        lt   -- Present in all applications -- gt       lt string name  quot google app id quot  translatable  quot false quot  gt 1 1035469437089 android 73a4fb8297b2cd4f lt  string gt        lt   -- Present in applications with the appropriate services configured -- gt       lt string name  quot gcm defaultSenderId quot  translatable  quot false quot  gt 1035469437089 lt  string gt       lt string name  quot default web client id quot  translatable  quot false quot  gt 337894902146-e4uksm38sne0bqrj6uvkbo4oiu4hvigl apps googleusercontent com lt  string gt       lt string name  quot ga trackingId quot  translatable  quot false quot  gt UA-65557217-3 lt  string gt       lt string name  quot firebase database url quot  translatable  quot false quot  gt https   example-url firebaseio com lt  string gt       lt string name  quot google api key quot  translatable  quot false quot  gt AIzbSyCILMsOuUKwN3qhtxrPq7FFemDJUAXTyZ8 lt  string gt       lt string name  quot google crash reporting api key quot  translatable  quot false quot  gt AIzbSyCILMsOuUKwN3qhtxrPq7FFemDJUAXTyZ8 lt  string gt       lt string name  quot project id quot  translatable  quot false quot  gt mydemoapp lt  string gt    lt  resources gt    You can refer to these links   https   firebase google com docs projects multiprojects Processing the JSON file  https   developers google com android guides google-services-plugin processing the json file

User · Answer

In my case someone had deleted APN SSL Certificates for my app in Apple development portal   I needed to create new certificates  Identifiers   My AppId   Push Notifications   Edit  Then I uploaded them to the Firebase project from console  Project Settings   Cloud Messaging   iOS app configuration   APNs Certificates   This solved the problem

User · Answer

Just an FYI  I was running into this error  even though I swear the android app I was testing was built with the latest greatest google-services json file and I could send from the FCM console to the app  I rebuilt the app after doing a Clean Project and now I can send to the app with the FCM token it registers  So  maybe try a clean rebuild before beating your head against the wall for too long

User · Answer

I found this solution   First I check server key is correct or not it was correct which is like  AIzaXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Then I check Sender Id like 79XXXXXXXX it was also correct  Main issue was in device ID UDID  to whom I have to send the notification  Actually DeviceId we got on android side in FCM is different than GCM  You can t use GCM created DeviceId in FCM

[firebase] FCM getting MismatchSenderId

Examples related to firebase

Examples related to firebase-cloud-messaging