NotificationPusher icon indicating copy to clipboard operation
NotificationPusher copied to clipboard

Incorrect invalid tokens of the APNs facade[v2.3.4]

Open wailaw opened this issue 7 years ago • 1 comments

I tested the APNs facade with a valid dev cert and an invalid device token in DEV environment. The response of the facade returned with the status code "8", which indicates that the token is invalid. However, there was nothing contained in $pushNotificationService->feedback() and $pushNotificationService->getInvalidTokens(). That invalid token instead appeared in $pushNotificationService->getSuccessfulTokens().

Everything's fine if a valid device token is used (the status is "0").

Here is the sample of the original response: "originalResponses": [ "a73b0f695b9f87f5dbd55f586ce093ef9dfa70d84855a39094dccbe3d3dd44c7" => Message { "id": 0 "code": 8 } ]

And the status code table:

0 - No errors encountered 1 - Processing error 2 - Missing device token 3 - Missing topic 4 - Missing payload 5 - Invalid token size 6 - Invalid topic size 7 - Invalid payload size 8 - Invalid token 255 - None (unknown)

wailaw avatar Jan 26 '18 02:01 wailaw

I received id=292869640 and code=8 But I didn't understand Why don't work Because I used same pem, password and deviceToken in other project and worked :/

edit


I tested using ./np push apns ... and worked.

edit 2


I tested again and not work more :P

eerison avatar Jan 28 '19 19:01 eerison