Like any other limited supply thing; there were so many slots available, and they filled up quickly. According to reports, more slots will be opened in the coming weeks. In the meantime, there are other things to test in the release.

No, that’s not it. It’s just that the available early access slots filled up quickly, and Apple is working to make more available in the coming weeks. https://x.com/markgurman/status/1849968331337630108

https://x.com/markgurman/status/1849968331337630108

It’s a staged rollout over time. See Gurman’s post: https://x.com/markgurman/status/1849968331337630108

The first set of open slots filled up quickly. They are working to add more slots in the coming weeks. Remember, this is an early beta. Source: https://x.com/markgurman/status/1849968331337630108

It was probably still downloading models. You can check in Settings → Apple Intelligence & Siri - at the top of the panel, it will mention if models are being downloaded, or if you’ve got an unsupported language setup. If it persists once models are downloaded, submit a Feedback via the Feedback Assistant.

”Time sensitive” notifications, to me, mean ones that shouldn’t be delayed and put in a scheduled summary, and that should appear at the top of the list of Notifications, and nothing more. I want them to go through the AI prioritizer so that Intelligent Breakthrough can work and inform me of the “Maybe Important” notification I just received. This is further reinforced by the fact that the User Notification framework documentation clearly states: The system makes every attempt to deliver local and remote notifications in a timely manner, but delivery isn’t guaranteed. The PushKit framework offers a more timely delivery mechanism for specific types of notifications, such as those VoIP and watchOS complications use. For more information, see PushKit. Since delivery isn’t guaranteed, I personally consider the delays being discussed in this thread to be insignificant. For applications like security applications where rapid timing is important, it seems that maybe PushKit should be used instead? On a side note,, I don’t see in the documentation where setting UNTimeIntervalNotificationTrigger? = nil would be valid, e.g., according to https://developer.apple.com/documentation/usernotifications/untimeintervalnotificationtrigger non-zero values for it are required. Shouldn’t this be using UNNotificationTrigger instead? e.g., from the example: convenience init( identifier: String, content: UNNotificationContent, trigger: UNNotificationTrigger? ) Probably doesn’t matter, since nil is nil, I guess.

After further research, it turns out that my personal understanding of “time sensitive notifications“ is basically correct. Per the documentation, the distinguishing factor is not time, but rather the ability to break through system controls like Notification Summary (that’s why they appear at the top of the list like I mentioned.) Time Sensitive notifications are similar to active notifications, but can break through system controls such as Notification Summary and Focus. The user can turn off the ability for time sensitive notification interruptions. https://developer.apple.com/documentation/usernotifications/unnotificationinterruptionlevel/timesensitive/#:~:text=Time%20Sensitive%20notifications%20are%20similar%20to%20active%20notifications%2C%20but%20can%20break%20through%20system%20controls%20such%20as%20Notification%20Summary%20and%20Focus.%20The%20user%20can%20turn%20off%20the%20ability%20for%20time%20sensitive%20notification%20interruptions.

About setting the trigger to nil causing undefined behavior, that’s completely wrong as well, as you can read in the documentation: trigger: The condition that causes the system to deliver the notification. Specify nil to deliver the notification right away. My point was about the code setting the variable to type UNTimeIntervalNotificationTrigger rather than type UNNotificationTrigger - I don’t know the internals of Swift well enough to know if that makes a difference or not, hence my question (and comment that it probably doesn’t matter since nil is nil) Time Sensitive Notifications break through Notification Summary and Focus: Agreed. But “break through” means they appear, e.g., the “Maybe Important” alert in the Reduce Interruptions focus. I fully expect future versions of this, once personal context is available, to result in some Time Sensitive Notifications not breaking through because the AI will know that I care about Duo notifications, for example, during the day, but not while I’m at the theatre. Re: PushKit — that was mentioned in the referenced section of the documentation. Not sure if it would be appropriate for your application or not. I could easily see a live activity being used for the sort of time critical user interaction I think you’re looking to do, if I understood correctly. E.g., I could see a live activity in my dynamic island with an open lock icon in green that turns red and closed to indicate the user needs to tap to go through that intervention, or something.

Yup, and if you go into Apple Intelligence & Siri, it will tell you it’s downloading models. Which it’s been doing all day.

Since the can of worms has been opened, I wanted to add a bit of a different perspective, having been using *OS 26 on a daily basis on all of my devices. Simply put, the design refresh is the absolutely most beautiful interface update I've seen. Not only that, but it's incredibly functional and smart -- it's the realization of the kinds of interfaces that have been science fiction until now. The fluidity is the really exciting (and useful) part that so many people seem to miss. The old way (and still the Android way) is very static. You can find out all about them from a screenshot. On the other hand, Liquid Glass isn't static. It's more of a gel at times; one that, like elegant, expensive crystal, captures, refracts and magnifies light. Controls even light with the energy from my fingertips when I press, slide and tap them. This fluidity plays out in making the interface much easier to use, and more efficient too. Instead of having, for example, the icons for several tabs displayed all the time, they can go away, until I want to change tabs, and then I press on the indicator, and it comes alive, lighting up, and showing the others, allowing me to change with a simple slide and release. 3 dots menu? Press and hold, and it transforms into the menu card that I can slide up to the one I want - with the selection lighting up for me. The only thing I'd like to see Apple do quickly is to get the message out countering the uninformed influencers' message of 'turn on reduce transparency to make it easier to read.' That's like taking a sledge hammer to hang a painting on the wall. Instead, the message should be that the design refresh meets Accessibility standards, and most people shouldn't have a problem -- but for those who still do, the 'Increase Contrast' toggle is a much better choice.

For the reference you asked for on this - it’s clearly stated that Foundation Models give access to the on-device models here: https://developer.apple.com/documentation/FoundationModels