Push notifications were not successfully delivered and have bad status

App & System Services Notifications APNS User Notifications

XVC_ OP

Created Nov ’23

Replies 17

Boosts 8

Views 5k

Participants 16

Hello everyone,

I have been working on a macOS app that utilizes push notifications for the past year. Up until recently, everything was functioning correctly. However, now I'm experiencing issues where push notifications are either not being delivered at all or are experiencing significant delays, sometimes up to 10 minutes. Setting the priority header to 10 hasn't made any difference. I am currently using development push notifications, but the issue persists when switching to the production environment.

I'm curious if anyone else has encountered similar problems. When checking the push console, it frequently reports that the device is offline, even though it's actually online ("discarded as device was offline"). Occasionally, notifications are delivered promptly, but this is becoming increasingly infrequent.

This issue has been consistently reported by our testers, particularly after they updated to macOS Sonoma. Any insights or assistance you can provide would be greatly appreciated.

Boost

shawnjung OP

Jan ’25

same here. 15.3 (24D60)

tritonus OP

This is still the situation in latest Sequoia I think.

I just started playing around with both push notifications and shared records this week, as I wanted to add collaborative features to my app. At first, I was wondering if I'm doing something wrong, because I don't get any notifications – not from my database subscriptions or even manually sent push notifications.

In some cases some notifications do come through after waiting for 5-40 minutes, but it feels a little fragile and unusable for collaborating on records.

However, here's the weird part: Restarting apsn from CLI or changing the network adapter will successfully transfer all of the subscriptions and manual test notifications, so it seems they are kind of working, but just won't get delivered.

I'm creating a CRDT-based app and I don't want to be polling constantly, but it looks like there's no other hope.