🐛 Bug Report: Fcm push notifications it gives unexpected provider error in the activity feed

[sujeet2singh]

📜 Description

Working on fcm push notification it gives unexpected provider error on the activity feed section although i have fullfilled all the steps mentioned in the documents provided. Like setting the credentials and adding deviceTokens before triggering notification I have attached the screenshots below for related issue.

👟 Reproduction steps

Go to activity feed after triggering push notification, => it gives unexpected provider error on the activity feed section although it gives success response on triggering notification

👍 Expected behavior

It show a notification with the proper data in the activity feed

👎 Actual Behavior with Screenshots

💻 Operating system

Linux

🤖 Node Version

v16.19.0

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• [X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• [X] I have read the Contributing Guidelines

Are you willing to submit PR?

None

[jainpawan21]

Hi @sujeet2singh, It looks like an error from FCM, Can you please check again your creds?

[sujeet2singh]

Hi @sujeet2singh, It looks like an error from FCM, Can you please check again your creds?

Thanks @jainpawan21

[im-perativa]

Hi @sujeet2singh, I have the same problem today. Would you like to share how you manage to fix it? I have already sucessfully test FCM without Novu in my app but when i tried to use Novu (with service account) it gives me unexpected provider error. Thank you