Posts

Post not yet marked as solved
0 Replies
746 Views
HelloWe are currently in the process of switching to Apns over HTTP/2 from our old implementation whick use the feedback service to determine expired devicetokens. We are using the following library https://github.com/relayrides/pushy to integrate with apns. We have verified that messages are being sent when the should be, that they fail if topic/devicetoken are erronous etc., but we are having trouble reproducing a 410 'The device token is no longer active for the topic'.Given that the timing for when (if?) a token gets invalidated is deliberately fuzzy we ended up with the following aproach (this is in production btw)1) find token in our log having reported by feedback service as being invalid the previous day in our daily poll of the service2) send notification to this id using the new api expecting a 410 responseHowever, we get a 200 OK message back ⚠ Is this expected behaviour?Is there a difference in the contract of the two approaches that we havent noticed? Does using both at the same time cause them to interfere with each other?Finally, is there a recipe or some sort of guaranteed approach to genereate a 410 response from server?
Posted
by oyvindolb.
Last updated
.