Subscriber does not have an active integration
I am using Novu headless on my frontend app, using FCM for push notification. When I send the push from backend I see in Novu activity history it says "Subscriber does not have an active integration
", but actually my device can see the push notification, is there any issues?
7 Replies
Hi @Yang, I'm an AI assistant for Novu. While a team member reviews this question, I'll see if I can find relevant sources for your question.
-----------------------------
While I generate an answer, here are some sources that might be helpful:
* Observability
* How to send PUSH notifications to iOS devices with FCM using Novu
* How to send push notifications in an Android app (react native) with FCM and Novu
* How to send push notifications to Flutter apps (Android & iOS) with FCM using Novu
-----------------------------
Answer
The message "Subscriber does not have an active integration" typically indicates a discrepancy with the subscriber's integration setup within Novu, particularly when trying to send push notifications. However, as you mentioned that your device can still receive the push notifications despite this error message, it might point towards a specific issue where Novu's activity feed is not accurately reflecting the status of the notification delivery due to how integrations or subscriber credentials are managed.
This situation could be related to the handling of multiple active push providers or the setup of subscriber credentials. There have been similar instances discussed in the community where errors were reported in the activity feeds, but notifications were still delivered successfully to devices. For example, a related issue was discussed where notifications showed errors on activity feeds, but push notifications were received on the device, which was to be addressed in a specific pull request (1) .
To resolve this, ensure that you have correctly set up the subscriber and associated device tokens with the right push provider (FCM, in your case) within Novu. This involves creating or updating subscriber credentials with the correct device tokens and ensuring that the FCM integration is correctly configured and active in your Novu dashboard. The process of associating device tokens with your subscriber's ID is crucial for the successful delivery of push notifications through the correct integration channel.
If the issue persists despite the correct setup, it might be related to a known bug or an integration-specific behavior within Novu that requires further investigation. In such cases, reviewing recent updates or discussions in the Novu community or GitHub issu
es might provide more insights into similar experiences or potential solutions.
@Yang that's very strange, are you using cloud or selfhosting?
I am using cloud
@Yang
Do you have multiple active push providers? but have not stored device token for any of the provider
I have 2 deactivated ones, and I saved a token for one of them
I have getting Same error @Pawan Jain .
I am using SelfHosting.
I dosn't have any other CHAT integration. trying to create 1st and
I created MSTeam integration and i am trying to update subscriber credential with webhook URL. but getting error from API like below.
{
"message": "Subscribers environment (64c36a101cc566874182051a) do not have active msteams-ZdVm06d95 integration.",
"error": "Bad Request",
"statusCode": 400
}