Now I can reproduce the issue 100% of the time: Register for APNS token Reinstall app Register for APNS token Go offline Send a push notification to the new token Send a push notification to the old token Come back online Expected: iPhone shows alert in Notification Center Actual: Notification is never shown In my opinion Apple should not allow alerts sent to invalid tokens to overwrite queued alerts for a valid token, but I'm guessing this it not an easy thing to change. In any case I suppose I will take your advice and implement a Notification Service Extension to attempt to work around this behavior. Thank you for all of your help Argun.

[quote='814463022, Engineer, /thread/768545?answerId=814463022#814463022'] Does this match what you have observed? [/quote] No. I'm pretty sure the third push never arrived in the Notification Center. To increase our confidence, I reproduced the issued again. This time I wrote everything down and took screenshots so I'm 100% sure of what happened: Sat Nov 16 22:25 EST 2024 — AirplaneMode=on, Wifi=off Sun Nov 17 03:53 EST 2024 — Amazon SNS reports successful API call to APNS: { "notification": { "messageMD5Sum": "...", "messageId": "...", "topicArn": "...", "timestamp": "2024-11-17 08:53:51.186" }, "delivery": { "deliveryId": "...", "destination": "...", "dwellTimeMs": 57, "token": "3f6e0931ae20851fdb17fe1add4a880a0449adabe130be01d08bf8fae79e2f09", "statusCode": 200 }, "status": "SUCCESS" } Sun Nov 17 05:30 EST 2024 — Wifi=on, Gmail push notification appears. No notifications from my app. Sun Nov 17 06:52 EST 2024 — Still 0 notifications from my app

Thank you for the fast reply. I'm not using other notification types. Only p=10, alert. So I would expect to see at least one Notification when I turn WiFi on. But I do not see any. I frequently experience the issue in production where I am sending a different payload each time (clock and timestamp are unique, and the message is usually different) so I don't think it's due to identical payloads I am not sure if I have the apns-ids because I'm using Amazon SNS to deliver the notifications. Perhaps it is the messageId or deliveryId field below? I also have a precise timestamp and device token below, if that is something you can use. I'm fairly certain this one failed to appear, but just in case you don't see anything unusual on your side, I will try to reproduce the issue again. Token: 3f6e0931ae20851fdb17fe1add4a880a0449adabe130be01d08bf8fae79e2f09 # 2024-11-12T11:12:36.528-05:00 { "notification": { "messageMD5Sum": "...", "messageId": "4f660f74-9108-5925-a5bf-50d911ba999e", "topicArn": "...", "timestamp": "2024-11-12 16:12:34.1" }, "delivery": { "deliveryId": "8ed6d103-a369-598d-9bbc-8eae23dbea58", "destination": "...", "dwellTimeMs": 67, "token": "3f6e0931ae20851fdb17fe1add4a880a0449adabe130be01d08bf8fae79e2f09", "statusCode": 200 }, "status": "SUCCESS" } I'll also keep trying to reproduce the issue using the APNS API directly, so I can specify an apns-id.

Normally I would use the CloudKit Push Notification tool delivery logs, but I have been unable to reproduce the issue in the CloudKit Push Notification tool so far. I can only try a few times per day due to the very long wait times sometimes required to reproduce the issue.