Post

Replies

Boosts

Views

Activity

Comment on Push notifications not received despite HTTP 200 from APNs — seeking help to identify the cause
Thank you for the guidance. We're updating our logging ASAP to capture and retain the apns-id from the APNs response headers for future cases. But some current "not received" cases happened before that logging existed, so we have no apns-id for them. Could you investigate these using just the push token and approximate send time? We have the tokens and timestamps. Also, we'd rather not post tokens or apns-id publicly, to avoid misuse. Is there a private channel (email or support) to share them?
3d
Comment on Push notifications not received despite HTTP 200 from APNs — seeking help to identify the cause
Thank you for the guidance. We're updating our logging ASAP to capture and retain the apns-id from the APNs response headers for future cases. But some current "not received" cases happened before that logging existed, so we have no apns-id for them. Could you investigate these using just the push token and approximate send time? We have the tokens and timestamps. Also, we'd rather not post tokens or apns-id publicly, to avoid misuse. Is there a private channel (email or support) to share them?
3d
Comment on Push notifications not received despite HTTP 200 from APNs — seeking help to identify the cause
Thank you for the guidance. We're updating our logging ASAP to capture and retain the apns-id from the APNs response headers for future cases. But some current "not received" cases happened before that logging existed, so we have no apns-id for them. Could you investigate these using just the push token and approximate send time? We have the tokens and timestamps. Also, we'd rather not post tokens or apns-id publicly, to avoid misuse. Is there a private channel (email or support) to share them?
Replies
Boosts
Views
Activity
3d
Comment on Push notifications not received despite HTTP 200 from APNs — seeking help to identify the cause
Thank you for the guidance. We're updating our logging ASAP to capture and retain the apns-id from the APNs response headers for future cases. But some current "not received" cases happened before that logging existed, so we have no apns-id for them. Could you investigate these using just the push token and approximate send time? We have the tokens and timestamps. Also, we'd rather not post tokens or apns-id publicly, to avoid misuse. Is there a private channel (email or support) to share them?
Replies
Boosts
Views
Activity
3d