We are currently testing our app with Urban Airship Engage
We are using named users for our notifications. When the app is running and the user is authenticated and paired to our hardware device we then associate a named user id to the channel id
Our backend then runs some code periodically to produce a list of named users that require a notification. We then tag those named users via api call /api/named_users/tags and then push a notification to all users with that tag using /api/push
Sometimes on my test app I get 3 notifications all at the same time. Yet when I query the push report using the push uuid the report shows the correct number of sends in this case, 2 sends. I'm assuming that indicates push was sent to 2 devices
I'm picking that this could be related to app uninstalls and re-installs where there could be some stale device id's floating around? And for some reason even though the api call shows two sends in the report that its being translated further down the track to 3 notifications to my iOS device.
Whats perplexing is when I query the named user in question (mark-1500855428-1-test-nibbl) and the channel id (81e2a8f6-30fe-46e3-bf14-015f50024445), I'm not seeing anything along the likes of multiple named users or channel id's associated to each other. Everything looks correct via the api calls I can make.
Even though push id (81f3527d-c4c0-4a34-b0af-cc0ffa387096) shows 2 sends, my phone got 3 notifications all at the same time from that particular push
Is there any way I can query for such stale data and potentially clean it up?
Is this even an issue of such stale data? I'm pretty sure the api calls we are making to tag the the users are correct and the response codes are all OK and the push report shows the correct number of sends
Any ideas on where to start?