New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ValidatingPushNotificationHandler not verifying expirationTimestamp #902
Comments
At a glance, that looks like it's just a mistake. I'll take a closer look shortly. |
I've looked more closely at this, and this is behaving as expected, though I recognize that the documentation could be clearer. The design intent is that callers can ask the mock server to report that a device token expired at a certain timestamp. The idea is that the timestamp should be in the past, but it's not technically required. The check you referenced is essentially asking "has somebody specified that this device is expired?" and not "should I perform some time check to see if it is expired?" I'll think about some ways to rephrase the docs to be clearer, but I do not believe there's any functional problem here. |
pushy/pushy/src/main/java/com/eatthepath/pushy/apns/server/ValidatingPushNotificationHandler.java
Lines 139 to 143 in e67df92
Is there a reason why the code is not actually verifying if it's expired but assuming if it exists then its expired?
Comment in
ValidatingPushNotificationHandlerFactory.class
makes it sound like it will be checked.The text was updated successfully, but these errors were encountered: