There seems to be a lack of clarity about how this Siri AI rollout is working. Does the indexing have anything to do with getting taken off the waitlist, or are they completely separate? Also, what is the expected wait time and has anyone gotten the new Siri after the initial wave of approvals (after 4 hours after the keynote)? The waitlist is extremely slow compared to the initial Apple Intelligence waitlist from a couple of years ago.

My phone no longer shows the waitlist for Siri and has the option to "Try New Siri." I select it, continue, continue and the settings change to "Siri (Beta)" and the waitlist option is no longer there, but when using Siri it's the old pre-Apple Intelligence Siri that activates (little bubble at the bottom) and it does not work. Going to Safari and typing "Siri://" opens the New Siri App, but it says "Siri Update in Progress; Adding support for Siri hasn't completed. Open Settings to check the status." The app does not show up in Spotlight. My phone is done Indexing and all signs point to my phone being enrolled to use the New Siri, but it isn't working at all and still has not shown up. I've tried restarting a few times. Anyone experiencing this too?

I just watched the "Build Intelligent Siri experiences with App Schemas" and I'm confused about how to integrate my app with the new Apple Intelligence + Siri in iOS27. I think it mentions specifically that Siri needs to adopt App Schemas, and that just adopting App Intents in my app isn't enough for it to integrate with the new Siri. Is that correct? The 'schemas' seem to be a narrow set of specific activities. What if my app's actions (or intents) don't match closely with it? For example, in my app, I have entities like Tags and Contacts. I can 'create tag' as well as 'add tags to a contact' as 2 different App intents. If I'm using just App Intents on their own, would these not map to the new Siri? I can also add a 'task' to a 'contact'. Would that possibly work with Siri? The videos just don't seem to make an effort to explain what is and what isn't possible.

What should we know about testing the new Siri and beta software on iPad vs iPhone if we do not have a space 17 PRO device for beta software testing? And can the new Siri AI be activated on an iPad? Any requirements? Any other testing options? Thank you.

It has been been days since WWDC without Siri at this point as it says it is still indexing. Does anyone have any suggestions?

For intents that return complex markdown, code snippets, or structured layouts, what are the rendering capabilities and resource constraints of custom SwiftUI views returned via Snippet inside the Siri voice overlay? Are interactive controls (like buttons, copy-to-clipboard, or scroll views) supported inside the Siri-overlay SwiftUI container?

I’ve found nothing about the waitlist, like when are there expected openings, how does an opening occur, and do I need to do anything else except join the waitlist? It’s been indexing for the same amount of time that I’ve been waiting for Siri, so is that a factor?

Hi, I joined the New Siri waitlist on June 8 (the day of WWDC 2026) and as of June 12, I have still not been granted access on iPhone or iPad — that's 4 days with no activation. I used the Terminal workaround on macOS 27 Golden Gate Beta (EnhancedSiriWaitlist → Enabled = NO), which successfully activated New Siri on my Mac. However, it has not synced to my other devices despite being on the same Apple ID with iCloud Siri sync enabled. Device details: Mac mini (macOS 27 Golden Gate Beta) — New Siri active ✓ iPhone (iOS 27.0 Developer Beta 1) — Joined Waitlist since June 8 iPad (iPadOS 27.0 Developer Beta 1) — Joined Waitlist since June 8 Steps already attempted: Multiple restarts on iPhone and iPad Toggled iCloud Siri sync off/on Toggled Siri off/on multiple times iCloud storage sufficient (200GB plan, 53GB used) 4 days seems far beyond normal rollout time. Is this a known issue? Is there anything on the account side that could be blocking activation? Thank you.

Do apps like Files, Safari, and Finder provide on screen data on request? I've got an entity that implements transferable, but Siri is consistently telling me that it is unable to export data from Files, Safari and photos, and does not seem to want to construct my entity. (it's an @PhotoAsset entity, and I've implemented @createAssets as well.) Is that true at the moment that Siri cannot read data from those apps? I'm not sure if this is a bug or a feature.

Share your experiences and any problems with Siri AI (iOS27 BETA) in detail. Describe which functions you particularly noticed, which difficulties you had, and in which situations Siri AI helped or disappointed you. Your detailed reports help us to talk about it in a targeted manner and find solutions or tips together.

With Siri AI and App Intents, we can surface content from apps. Can we add guardrails or configure what Siri can or cannot say when dictating content?

Its been 3 days since i had requested for Siri AI , still in the waitlist. This is disappointing .

Inquiring if there are any bugs in the wait list for obtaining access to Siri AI. Most developers I know have received access at this point, my devices are still waitlisted. Are their steps outside of region / language that can cause longer wait times for admittance and are there steps I should take to ensure their is not a hitch in the system, or is this truly a slow rollout and I will just be a week behind the curve in development ?

How are some people getting access within 10 minutes while I've been waiting for over a week? In fact, it's been 48 hrs since I joined the waitlist. This is honestly ridiculous. I've met all the requirements, enabled every necessary setting, and still have no access. Meanwhile, others are getting approved almost instantly. If the rollout is based on a waitlist, then it should be handled fairly and consistently. Waiting this long for a feature update is extremely frustrating, especially when there has been little to no communication about the delay.

Does the App Intents framework expose the user's active spoken Siri locale (e.g., ja-JP, fr-FR) directly within the perform() context, or must the extension rely on the system's global locale setting? If a user switches Siri's language dynamically, how is that locale string propagated to the intent execution block?

Are there specific Entitlements (com.apple.security.temporary-exception.files.absolute-path.read-write or network exceptions) required to allow App Intents to talk to local UNIX sockets or loopback interfaces (127.0.0.1) without triggering sandbox violations?

Can App Shortcuts (and their trigger phrases) be generated or translated dynamically at runtime based on user-defined configurations (e.g. download-on-demand language models or custom voice aliases), or must all voice shortcuts and translations be statically declared in the application's compiled String Catalogs (.xcstrings)?

How does the App Intents framework support streaming spoken voice (TTS) output for long-form text responses? Is there an API (such as an asynchronous sequence or buffer stream) that allows Siri to begin speaking a response while the underlying AI engine is still generating the remainder of the text?

Hello everyone, I am testing how Siri interacts with web pages on iOS devices. When a user utilizes Siri voice commands to search for or open a specific website, Siri usually processes the request and opens the result inside the Safari browser. As a web developer, I want to know if there are any specific HTML meta tags, Schema markup, or SEO best practices that we should implement. This is to ensure Siri can accurately recognize the website's name, brand, and content. What are the simplest ways to make a static web page friendly for Siri voice search? Thanks in advance!

According to https://developer.apple.com/download/files/CarPlay-Developer-Guide.pdf , apps with entitlement com.apple.developer.carplay-driving-task are allowed to use voice control. In my current implementation the voice recording working fine but the voice response (AVPlayer with category "playback set") does not output any audio. I suspect that it is a entitlement limitation because if I quickly tap to play a music while the voice assistant AVPlayer is "playing", then I can hear the response, but without this trick it stays playing but mute. In parallel I have now requested com.apple.developer.carplay-voice-based-conversation entitlement , but I don't even know if when approved I will be able to use 2 entitlement for the same CarPlay app. Long story short: 1 - Should an app be able to play audio responses when it's CarPlay entitlement is com.apple.developer.carplay-driving-task? 2 - If not, can I combine entitlements com.apple.developer.carplay-driving-task and com.apple.developer.carplay-voice-based-conversation?