Azure Notification Hubs
An Azure service that is used to send push notifications to all major platforms from the cloud or on-premises environments.
325 questions
Why Notification Hub installations are not removed on expiration time?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 60%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOP%3C/text%3E%3C/svg%3E)
Oleksandr Pastukhov
0
Reputation points
Hello,
we're working on an application that uses Azure Notification Hub for sending push notifications. The application utilizes Notification Hub .NET SDK v4.2.0 to communicate with the Notification Hub. To register a device for push notifications, the app creates an installation with an expiration time specified and persists it in the Notification Hub using the _hubClient.CreateOrUpdateInstallationAsync(installation, token) method of the SDK. However, per our observation, such installations are not removed after they pass the expiration date. For example, in the screenshot below you can see that there is an installation present in the Notification Hub that has an expiration date set to 07/01/2024, so it has not been removed considering that two days have passed since the expiration time.
Is it a bug in the Notification Hub or are we missing something?
If any more details are needed, please let me know.
Sign in to answer