Skip to content

Commit 8b50b3b

Browse files
committed
Tweaks
1 parent c1b3b0d commit 8b50b3b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/notification-hubs/notification-hubs-push-notification-faq.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -183,11 +183,11 @@ sections:
183183
Yes. All Notification Hubs management operations update the Azure Activity Log to which is exposed in the [Azure portal](https://portal.azure.com). The Azure Activity Log offers insights into the operations performed on resources in your subscriptions. Using the Activity Log, you can determine the what, who, and when for any write operations (PUT, POST, DELETE) made for the resources in your subscription. You can also understand the status of the operations and other relevant properties. However. the Activity Log does not include read (GET) operation.
184184
185185
- question: |
186-
Does Notification Hubs detect uninstallation for iOS or Android?
186+
Does Notification Hubs detect uninstallation?
187187
answer: |
188-
There are two ways to handle this. If you stored the device as a `Registration`, the first time you send to that registration and the PNS responds with an error status code that indicates that the device is not valid, it's deleted from your notification hub.
188+
If you stored the device as a `Registration`, the first time you send to that registration and the PNS responds with an error status code that indicates the device is not valid, the device is deleted from your notification hub.
189189
190-
If your devices are stored using the `Installation` APIs, they are not deleted in the scenario above. This decision was made to preserve tags and other metadata about a particular user that might be relevant if the user reinstalls.
190+
If you stored your devices using the `Installation` APIs, they are not deleted in the scenario above. This decision was made to preserve tags and other metadata about a particular user that might be relevant if the user reinstalls.
191191
192192
For both registrations and installations, you can set an expiration so that the device is automatically cleaned up at a given time. A common pattern is to have your client application update that expiration date once a day to move it back as long as the user is using your application.
193193

0 commit comments

Comments
 (0)