search

Azure / azure-notificationhubs-dotnet

.NET SDK for Azure Notification Hubs
MIT License
70 stars 119 forks source link

[Query] 4.2 FCMV1 #321

Closed njhampsh closed 3 days ago

njhampsh commented 1 month ago

I've upgraded to 4.2 of Notification Hub, I've noticed differences in the PNS Errors returning when a device is no longer registered when moving from FCM to FCMV1. While using FCMNotification to build the message and check the NotificationID after sending (if the device no longer exists) the expected response is Expired Channel

<PnsFeedback xmlns:i="
[http://www.w3.org/2001/XMLSchema-instance"](http://www.w3.org/2001/XMLSchema-instance%22)
xmlns="
[http://schemas.microsoft.com/netservices/2010/10/servicebus/connect">](http://schemas.microsoft.com/netservices/2010/10/servicebus/connect%22%3E)
<FeedbackTime>2024-05-31T19:46:12.4770547Z</FeedbackTime>
<NotificationSystemError>ExpiredChannel</NotificationSystemError>
<Platform>gcm</Platform>
<PnsHandle>xxxxx</PnsHandle>
<NotificationId>NH-xxxxx</NotificationId>
</PnsFeedback>

When upgrading to FCMV1 and using FCMV1Notification and checking the NotificationID after sending, it's now returning UnknownError.

<PnsFeedback xmlns:i="
[http://www.w3.org/2001/XMLSchema-instance"](http://www.w3.org/2001/XMLSchema-instance%22)
xmlns="
[http://schemas.microsoft.com/netservices/2010/10/servicebus/connect">](http://schemas.microsoft.com/netservices/2010/10/servicebus/connect%22%3E)
<FeedbackTime>2024-05-31T15:03:54.7892952Z</FeedbackTime>
<NotificationSystemError>UnknownError</NotificationSystemError>
<Platform>fcmV1</Platform>
<PnsHandle>xxxxx</PnsHandle>
<NotificationId>NH-xxxxx</NotificationId>
</PnsFeedback>

Is this the expected behavior for moving to FCMV1?

lomagdal2 commented 3 days ago

We rolled out a hotfix that fixed the unknown error pns feedback issue a couple of weeks ago. This issue is now fixed.