Self hosted Novu with Firebase provider error
Hi Team,
We are using Firebase provider for push notifications on self hosted novu, and in our production environment we see this error when we trigger notifications on novu activity:
"Sending message failed due to "Operation is not implemented, or supported, or enabled. Raw server response: "{"error":{"code":501,"message":"Operation is not implemented, or supported, or enabled.","status":"UNIMPLEMENTED"}}"""
Could you guys please shed some light on this error? what could be causing this?
31 Replies
https://github.com/firebase/firebase-admin-node/issues/2687
https://groups.google.com/g/firebase-talk/c/1OHTEwSzZYU
https://stackoverflow.com/questions/78894668/phone-registration-error-unimplemented-gcm-error-on-a-device-using-javascript
I found similar issues for older Firebase SDK versions
GitHub
messaging/unknown-error when using sendEachForMulticast · Issue #26...
Operating System version: AWS Lambda Firebase SDK version: firebase-admin 12.3.0 (but also previous versions) Firebase Product: message notification Node.js version: Node.JS 18 NPM version: 9 I hav...
Stack Overflow
PHONE_REGISTRATION_ERROR / UNIMPLEMENTED GCM error on a device usin...
We are using devices which has Linux OS, javascript enabled (using node.js). We are using google FCM to receive notifications. We are using a javascript library (added register() here) to get the fcm
@Soumith, you just advanced to level 2!
Hey @Soumith
This issue is happening due to deprecate
sendMultiCast method. it should be replaced with sendEachForMulticast
We fixed this issue in cloud but have not released new docker images that will include this fixHi @Pawan Jain,
Do you know when this fix will be released?
@Soumith
We are planning to release new docker images early October
shit, this is fucked up for self-deployed instances using push notifications in production!
I would treat this as critical thing to fix as soon as possible, since it means that push don't work anymore to fcm. And I understand that you concentrate on cloud version and self-hosted are more or less on their own, but missing a build/image for such critical fix really makes our company seriously reconsider using novu, even if self-hosted.
Agree!!!
@Pawan Jain This is breaking in production and we cannot afford customers losing notifications for a month, as this is a hotfix, can you guys please provide interim solution?
@Soumith @frnandu
We are working on a hotfix for this issue.
I will keep you updated in this post
Thank you!
Thank you @Pawan Jain!
Hey all 😄 the team is working hard to make sure we can release a hotfix soon. @Pawan Jain will follow up ASAP with more updates as the team roles them out.
Thanks for understanding and being an amazing community!
Thanks for the update @Tomer Barnea!
I'm having the same issue. Hope to get this hotfix soon because it's blocking my release to production.
We are looking for immediate fix...currently all push notifications stopped.
@Pawan Jain can you please give us an update on this topic.
Small Update on this:-
We have published docker images with tag
0.24.3
However, there is one issue with api docker image due to which this tagged version can not be used.
Sok from our team is working on resolving that issue
@Soumith @Eduardo Santos @frnandu @Chandan kumar @Fakhar @Adil Javed
Thanks for being patient with us.
- update your worker and other services docker image tag to 0.24.3 except api service
- if you see below error with api tag 0.24.1 and 0.24.2. use API docker image tag 0.24.0
checkout this file changes
https://github.com/novuhq/novu/pull/6488/files#diff-3553fc766756fb977edd9560e25cd13d2f8e0eb268a1f91760ad298482766b75Thank you so much @Pawan Jain! We'll test and let you know 🙂
Please let us know once this is merged.
hope this new docker image release soon
You can go ahead manually change the version in your docker-compose.yml file
@GetWrong
We released 0.24.3 version.
Thanks @Pawan Jain , I'll talk with my team here.
Hi @Pawan Jain I've encountered an issue while running novu-api 0.24.3. Please find stack trace below
@Katya Kuzmenchuk , use
0.24.0 tag for api service, for all other services you can use 0.24.3 tag@Pawan Jain we're now having 2 errors for the same push step:
@Eduardo Santos
These errors are different
https://stackoverflow.com/a/56218146
Stack Overflow
"Requested entity was not found" error when trying to send a push n...
I'm trying to send a multicast notification via FCM from a Firebase Cloud function with the following code:
const message = {
tokens: recipients,
notification: {
title: title,
...
Stack Overflow
FCM getting MismatchSenderId
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, ...
But I'm able to send the push to the same device tokens directly using FCM Api
So, there could be the case you have different service.json of different project in Novu and token was generated using other fcm project
It's working now, it might be some delay or caching.
Hello! We just did the proposed updated above on self-hosted instances.
We get the "Requested entity was not found error" mentioned above.
@Eduardo Santos was it finally a cache issue?
It is already 30 minutes after the update and push notifications still have this error
@rolkool, you just advanced to level 1!
@rolkool
Requested entity was not found error error occurs if deviceToken is not generated using same credentials as same as service.json credentials