-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
MismatchSenderId #1215
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
Comments
have you checked that: http://stackoverflow.com/questions/29163089/node-gcm-server-receive-error-mismatchsenderid |
Also, the senderId is never used internally by the push adapter. You could remove that option from the configuration. This seem solely related to an API key problem. |
@flovilmart i have checked the url that you have sent and also removed the senderId from my config. object but still got the same error |
So I'm not sure what the issue is. We use node-gcm and I've run some tests and with a valid API key from Google cloud platform, I manage to get the push sent |
Thanks @flovilmart , Still need a help about this issue. |
Can you try generate another API key ? Look at node-gcm documentation, I believe they have a debug mode you can enable with environment variables |
@fabuhelow, 2 things to check here:
|
@fabuhelow did you get to the bottom of it? This is however not related to parse server but to https://github.com/parse-server-modules/parse-server-push-adapter Would you reopen on the other repository if you still face problems? |
Hi,
I have tried to push new notification from my parse-server, but i have got the following error:
GCM request and response {"request":{"params":{"priority":"normal","data":{"time":"2016-03-27T13:15:43.556Z","push_id":"K8QBFFDDe1","data":"{"title":"The Shining","alert":"All work and no play makes Jack a dull boy."}"}}},"response":{"multicast_id":8205105798183603000,"success":0,"failure":2,"canonical_ids":0,"results":[{"error":"MismatchSenderId"},{"error":"MismatchSenderId"}]}}
I have checked my google sender id and API key and they are valid.
My parse-server version is 2.2.2
The text was updated successfully, but these errors were encountered: