Thanks; it does seem like it's been fixed in iOS16 and macOS13 betas.

Any thoughts on how to communicate between app extension and the parent app? On iOS, I would write to a plist file, and the iOS app would read the plist file when it became active and update accordingly ... but wondering if there's a better way on the Mac (while respecting sandboxing).

Filed FB9162707

Thank you; that's very helpful. I'll have to look into building some queuing mechanism I suppose. I don't particularly understand why they can't update the limits, considering that it's been there since UILocalNotifications was introduced in iOS4, and everything under the sun has changed since then!

Thanks for the response. Implementing a server, with push notifications and scheduling, is a big task, so it would be really nice to have a work-around locally. One thing I wanted to ask ... is there a limit to how many UNCalendarNotificationTriggers we can setup in the app? With UILocalNotifications, there was some limit for 64 (or was it 128) notifications that could be scheduled at one time within an app. Does that limit also exist for User Notifications (if so , is it a higher limit than before)? If the notifications limit wasn't an issue, then one can theoretically schedule out calendar notifications to fire at each repeat interval, maybe for the next 5 repeat intervals, and then recalculate when the app is launched at some point.

I meant to say '128' (instead of the emoji)!