-
Notifications
You must be signed in to change notification settings - Fork 22
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
Getting HTTP 500 Internal Error after adding FCM Service Account File #149
Comments
I'm having the exact same problem, I'm unable to register any new device for push notifications because of this. I was trying to set up
After debugging in
when the library executes the The library calls this endpoint by passing a In the documentation mentioned above, the endpoint for registering to FCM apparently requires a I tested the same call in Postman by explicitely passing a There seems to be an internal issue going on on Pusher Beams API side, could anyone from the Pusher team please have a look at this? |
yeah... i ve the same issue too... possible help us with this please.. |
why is no one looking into this???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? what am i paying for???? |
After adding the FCM file on our Dashboard, we started receiving information on our Error Tracking:
POST https://{INSTANCE_ID}.pushnotifications.pusher.com/device_api/v1/instances/{DEVICE}/devices/fcm [500]
We have over 23k occurrences of this event in our dashboard, plus notifications aren't currently working.
We'd like to at least remove the Service Account file from the Dashboard for now, but that also doesn't seem to be an option on the Dashboard UI.
The text was updated successfully, but these errors were encountered: