Detect invalid device tokens about java-apns HOT 7 CLOSED

Is there any advice or best practice for dealing with the problem of invalid device tokens? What even constitutes an "invalid" token?
All I can think of is using an Always reconnect policy, but that doesn't seem to be a good choice for a production environment.

from java-apns.

With the new support for enhanced push notification protocol, your ApnsDelegate will be notified if a connection gets closed due to an invalid device token. ApnsDelegate#connectionClosed() will be called with DeliveryError. MISSING_DEVICE_TOKEN argument.

from java-apns.

Great! Is that available in the 0.1.5 download, or do I have to build from source myself?

from java-apns.

It's available in the 0.1.5 download (I recommend using maven or Ivy though). Don't recall if you need to enable the enhanced service in ApnsServiceBuilder.

from java-apns.

For those who see this thread later:
In the 0.1.5 download, the default mode for ApnsServiceBuilder is to use "enhanced error-checking" mode. I did notice that the version of ApnsServiceBuilder in 0.1.5 has a bug that prevents you from disabling "enhanced error checking" mode; it was apparently fixed later (see 8002bb5)

from java-apns.

Thanks for bringing this up. Disabling enhanced error-checking mode will be available again in 0.1.6. I'll make a release soon. However, I'm considering breaking backward compatibility to fix some issues with the API in light of the new functionality.

from java-apns.

Now that I've updated our production environment to use 0.1.5 and put in an ApnsDelegate that just logs on connectionClosed(), I'm seeing a few closes due to INVALID_TOKEN. I understand that this can be caused by a development token being sent to the production pns server; is there any other potential cause of INVALID_TOKEN?

from java-apns.