-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when sending push notification for android, I got MismatchSenderId error #704
Comments
I have created GCM credentials and enabled Google Cloud Messaging in google cloud platform. I also added the push senderId and apiKey in Parse Server's index.js
when I test sending push using the following REST api call:
I saw this log:
why does it return MismatchSenderId error? |
Was this an installation migrated from parse.com? Is that the senderId which was used to register this device? |
How will installation affect REST api call from command line? In my test, there are no installations migrated from parse.com. When I delete all the installations on mongodb and run the test push command, server logs shows the same error of MismatchSenderId. It also logs |
Odd! I tested again and now push is successfully received. Nothing has changed in my code. I suspect something fishy was going on in GCM |
I found the problem, I put
outside the application section in the AndroidManifest. The app still compiles and runs but I guess the sender_id is not used from the client? When I move it to inside application, push works. @gfosco Thanks. |
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
-[ ] You've met the prerequisites.
-[ ] You're running the latest version of Parse Server.
-[ ] You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
Steps to reproduce
Logs/Trace
The text was updated successfully, but these errors were encountered: