Closed jobomix closed 4 years ago
Hi @jobomix ,
Base on the compose file you've sent, FCM server auth token seems to be missing, thus there is a problem with authorization with FCM.
Hi @rslota,
Thanks for the quick response.
The token.json is under /opt/app/priv/fcm/token.json. Do I need to add an extra config variable? BTW I ve just tried the latest docker image with the same config and it all works, so it looks like the problem is inherent to the 1.0.6. I would prefer to use a stable release for what I need to do
Current stable release 1.0.6
does not support FCMv1 API, which I'm assuming you're trying to use. 1.0.6
supports so called "legacy" FCM API, which requires string-only token configurable via env variable. Please refer to documentation in README.md
for correct version of MongoosePush. In this case - https://github.com/esl/MongoosePush/blob/1.0.6/README.md .
OK that explains it.
Thanks
Hi,
I am running mongoosePush 1.0.6 with Docker I am using the following end point
POST /v2/notification/{device_id}
to send a message to FCM. I got a valid device_id and I tested it through FCM. It all works fine. I am making a post to my endpoint with the following payload :{ "service": "fcm", "data": { "body": "notification's text body", "title": "notification's title" } }
When posting I get the following error
My docker compose:
The cert is valid on the https endpoint. did I do something wrong?
Thanks