Azure的推送通知中心不发生故障后工作 [英] Azure push-notification hub don't work after failure
问题描述
在服务器端，我们使用的Azure SDK与Azure工具版本：2.2
On the server side, we are using Azure with SDK Azure Tools Version: 2.2
我们派一个失败的iOS推送通知（APNS错误也出现在仪表盘）。这个失败后，推通知不会对此标签和轮毂所有的时间工作。
我们如何解决不清除所有注册并创建一个新的标签这种情况呢？
We send push-notifications on iOS with a failure (APNS Errors did appear in Dashboard). After this failure, push-notifications don't work on this tag and hub all the time. How can we fix this situation without clearing all registrations and creating a new tag?
通常情况下是这样的：
1.标签工作正常。
2.我们注册错误的证书，例如一些设备。错误的仪表板。
3.标签不能完全工作。错误的仪表板。其中previously得到通知的设备没有得到它了。
Usually scenario looks like this: 1. Tag works fine. 2. We register some device with wrong certificate for example. Errors in dashboard. 3. Tag doesn't work totally. Errors in dashboard. Devices which previously got notifications doesn't get it now.
我们可以改变一些东西，使老设备能够得到通知（之前步骤2中添加）？
Can we change something to make old(added before step 2) devices able to get notifications?
推荐答案
通知中心是APNS证书/令牌非常敏感。有几个规则：
Notification Hub is very sensitive to APNS certificates/tokens. There are couple rules:
-
避免使用无效的（假的）设备令牌或之前清理它们发送到实际设备。如果需要运行一些单元测试用假令牌那么最好是建立用于该目的的独立的集线器。
Avoid to use invalid (fake) device tokens or clean them up before send to real devices. If it is required to run some unit tests with fake tokens then it is better to create separate hub for such purpose.
当是时候从沙箱APNS证书/终端切换到它需要清理所有现有APNS注册的生产企业之一（或后）。甚至更好的方式 - 只需创建测试和生产独立的集线器
When it is time to switch from the sandbox APNS certificate/endpoint to the production one (or back) it is required to clean up ALL existing APNS registrations. Or even better way - just create separate hubs for test and for production.
这篇关于Azure的推送通知中心不发生故障后工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
