@Reddy, Santosh Thanks for reaching here!
- If the
CreateOrUpdateInstallationAsync
method is not throwing any errors and is returning a successful status code, it is possible that the installation is not being created due to some other issue. - One possible reason could be that the connection string used to connect to the notification hub is incorrect or has expired. You can check if the connection string is correct and has not expired by creating a new connection string and using it to connect to the notification hub.
- Another possible reason could be that the installation ID is not being generated correctly. You can try generating a new installation ID and see if that resolves the issue.
- Also Using installations enables you to do partial registration updates. The partial update of an installation is requested with a PATCH method using the JSON-Patch standard.
- To highlight when using
CreateOrUpdateInstallationAsync()
, though the name has 'update' in it, NotificationHub documentation advises us to usePatchInstallationAsync()
with patch-update process. PatchInstallationAsync() - If the issue persists, you can try using the Notification Hubs REST API to create and manage installations.
Let us know if further query or issue remains.