UNNotificationRequest Scheduling Limitation

I have read from previous posts in the forum and in StackOverflow that the limitation of 64 notification is still present with the current iOS18 version right? Inside testflight I was not able to reproduce this limit and was wondering if it only applies to the AppStore.

Is it only a limit of scheduled notifications or is there also a limit of delivered notifications ? I find the Apple documentation lacking detail in this regard. If the latter is the case, I will not bother building a notification manager to deal with frequent notification scheduling.

thank you in advance

S.

Is it only a limit of scheduled notifications or

The limitation is specifically on how many local notification requests you can schedule. Note that because of how notifications triggers work, this limitation does not directly translate to how many pending or delivered notification will actually occur. That is, scheduling a notification to fire every 5 minutes can be done in a single request but is going to quickly deliver a lot more than "one" notification.

is there also a limit of delivered notifications ?

I'm not aware of any specific limitation, though it's probably not truly "unlimited". In practice, an app that's dealing with very high notification volume (for example, messaging apps) needs to come up with some kind of system for organizing it's notification "stream" just to ensure a reasonable user experience.

In concrete terms, I don't know what the system will do if you hand it a single notification stream with 1000 notifications, but I do know that I wouldn't want to try and scroll through it.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

Thank you Kevin for the clear answer. I think that clarifies my doubt. Can you confirm that in the App Store I will get the same behavior that I experience in TestFlight using UNNotificationRequest ? Or do I have to keep into account something else ?

Best,

Stefano

UNNotificationRequest Scheduling Limitation
 
 
Q