Notifications continue to send after deleting an installation

buyani.mhlongo 30

Notifications continue to send after deleting an installation can we get help on this please

1 answer

Siva Nair 410 Reputation points Microsoft Vendor

2025-02-17T15:23:38.8166667+00:00
Hi buyani.mhlongo,

To fix the issue, Lets follow these steps:

Verify Installation Deletion- Run the following command using the Azure CLI to check if the installation still exists: az notification-hub installation show --hub-name "<YourHubName>" --resource-group "<YourResourceGroup>" --namespace-name "<YourNamespace>" --installation-id "<YourInstallationID>".

If the installation still exists, try deleting it again: az notification-hub installation delete --hub-name "<YourHubName>" --resource-group "<YourResourceGroup>" --namespace-name "<YourNamespace>" --installation-id "<YourInstallationID>".

If the installation deletion did not fully remove the registration, list all active registrations: az notification-hub registration list --hub-name "<YourHubName>" --resource-group "<YourResourceGroup>" --namespace-name "<YourNamespace>". If any stale registrations are still active, delete them manually.

Clear Local Device Tokens-For Android (FCM): Call FirebaseMessaging.getInstance().deleteToken() to remove the FCM token. Ensure your app properly handles token refresh events.

Monitor Logs and Incoming Requests- Check if your backend system is still sending notifications to an old installation ID or device token. You can log outgoing notification requests to verify.

Force Expiration for FCM/APNs- For FCM, you can try forcing the token expiration:

curl -X POST -H "Authorization: key=<YOUR_SERVER_KEY>" \ -H "Content-Type: application/json" \ -d '{ "to": "<DEVICE_TOKEN>", "data": { "action": "logout" } }' //mention you API endpoint.

For APNs, ensure you’re handling feedback properly so expired tokens are removed.

If you need any further assistant, do let me know.

If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
Please sign in to rate this answer.
Siva Nair 410 Reputation points Microsoft Vendor

2025-02-19T04:26:43.76+00:00

Hi buyani.mhlongo,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

buyani.mhlongo 30 Reputation points

2025-02-19T06:35:15.08+00:00

That is rather a very long process @Siva Nair on something that should be done by function DeleteDeviceInstallation(deviceInstallationId). Why do we have to do all mentioned above?

Siva Nair 410 Reputation points Microsoft Vendor

2025-02-20T05:24:09.4466667+00:00

Hi buyani.mhlongo,

Yes, calling DeleteDeviceInstallation(deviceInstallationId) should be enough to stop notifications. However, the reason for the extra steps is due to how Azure Notification Hubs and push notification services (APNs/FCM) work:

Propagation Delay: When you delete an installation in Azure Notification Hubs, it may take some time for the change to propagate across all servers.

Caching by APNs/FCM: Both Apple Push Notification Service (APNs) and Firebase Cloud Messaging (FCM) cache tokens. They may continue to deliver messages until they detect that the token is no longer valid.

If notifications are still being sent, it’s usually because the device token is cached by APNs or FCM.

Azure Notification Hubs can’t directly invalidate these tokens. You need to ensure the device itself clears or refreshes the token.

Normally, you only need to call DeleteDeviceInstallation(deviceInstallationId).

If notifications still occur, follow these steps:

Clear the device token on the device itself. This forces FCM/APNs to generate a new one.

Check for stale registrations on your backend.

Wait a short period to allow for propagation.

This isn't an issue with Azure Notification Hubs, but rather how APNs/FCM handle token caching.

https://learn.microsoft.com/en-us/azure/notification-hubs/configure-notification-hub-portal-pns-settings?tabs=azure-portal

If you have any further assistant, do let me know.

If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Siva Nair 410 Reputation points Microsoft Vendor

2025-02-21T06:45:42.2866667+00:00

Hi buyani.mhlongo,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Buyani Mhlongo 0 Reputation points

2025-02-21T10:00:46.42+00:00

@Siva Nair I think thats incorrect notifications are sent through Azure Hub not FCM then Azure Hub ,if Azure Hub deletes the data it will not reach FCM ,but thanks Siva even though this does not really solve the problem we have since I am not the only one with this issue.I will not accept this as an answer until the DeleteInstallationAsync function does what you have mentioned above such that there is no caching .

Siva Nair 410 Reputation points Microsoft Vendor

2025-02-28T07:04:35.7766667+00:00

Hi Buyani Mhlongo,

Yes you are correct, The issue is due to caching and propagation delays in Azure Notification Hubs. It’s not an FCM or APNs issue because ANH handles routing.

Use UpdateInstallation to force a cache refresh before deletion. Verify deletion with the REST API. Clear tokens on the client side to ensure notifications stop. Consider using tags as a soft delete mechanism. Delay sends and implement retry mechanisms to handle propagation.

https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-registration-management

https://learn.microsoft.com/en-us/rest/api/notificationhubs/installations/delete

If you have any further assistant, do let me know.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Notifications continue to send after deleting an installation

1 answer

Your answer