Please advice if this is correct 100% throttling behaviour (3 hours, 100% blocked), if no other notification is received? What should I do, to reset the throttling counter (it doesn't seem to be reset after any time, not after 1hr, nor 24hrs). I consider, as last resort, creating a new Apple ID on my iPhone. Would this strange workaround help?

I can't provide apns-id, as Google FCM is the originator. I can provide you APNs token. Please advise how I should share it, if you need it for the analyzis. I turned off the notif's on my dev. for all apps usually sending notif's, except mine. I sent 4 notif's from 4 different devices (1 iPad, 4 Android) on 15-08-2025, 9:04-06 UTC. None was received within more than 3 hours. I received just one notification for app I forgot to turn the notif's off. I keep the device waiting and do not open app.

You are right. Thank you for your post. I was 100% I haven't changed anything in my purchase view, that's why I was focused on status issues. But I did a stupid change, which blocked purchase items display.

Thanks for your reply. I will check the Notification Service Extension. However, what I really observed is that background notification worked fine before the rejection. Not only when running from Xcode. They worked when app was run from TestFlight. Sometimes notifications were received almost instantly, sometimes with delay. After the refection, they are NEVER received in the background. Only when I reopen app (which you see as successful delivery, which is really not) or at sig. loc. change.

Please read the detailed answer in my post below I have finally mastered the GitHub in Xcode. Here is the link to the project: AA_Loc_Leak_TestProj on GitHub

Once I started to use Xcode more and more the problem seems to grow bigger and more annoying. The battery is drained dramatically. Now when I start Xcode I start Process Monitor simultaneously, to kill bad processes once they start eating up power. And it happens now every time I launch Xcode, and keeps returning after a while in one session. Sad that Apple just ignores it (new complains are added and no answer).

Well, it doesn't help. Preview still causes this problem and I do not know if the setting can be set for it. I did it for Simulator.

No. It didn't help. The problem returned. Apparently killing the SpringBoard also helps for some time only, as after a while it keeps overheating computer.

For now the problem cease to exist after reinstalling iOS image (17.0) for the emulator and removing old images from the user's cache directory. I will post a comment if situation changes.