We are also facing the same issue. I opened a Technical Support Issue. The support engineer could see the problem happening. He said, he is going to contact the APNS team regarding this issue. We initially thought its the JSON payload format that could be causing the issue. But we fixed and it is still happening. We haven't tried to remove the ID parameter from the payload as we need that parameter in the payload. We thought Apple will fix it. Any other update on this issue?

Here is the update: Apple confirmed that the issue is with having "id" field inside the "aps" dictionary. They asked us to keep the "id" field outside the "aps" dictionary to stop the issue from happening. Here is a much simpler fix to this issue. Someone below found that by changing the return type of the ID field value fixed the issue. We tried that as removing the id field will impact our current client. And that worked. We are planning to do the right way afterwards. Hope this helps.