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.

Okay, so i’ve been on the waitlist since Monday, roughly about 107 hours, and still nothing, i have iPhone 16 pro, and what’s frustrating some people got it like after 2-3 hours, maximum 3 days, but now its getting really frustrating , hope today i will get it!

Hello, the only way to make Siri AI pick up my intent, or action on my intent + entity is that if BOTH use an schema? For example, I have an intent that adopts a schema, but my entity doesn't. That means Siri AI can't do anything with my intent? What if neither use a schema? Siri AI can't do anything with it? I'm asking because schema seems limited to only few domains which I'm not sure how I'll integrate with my apps.

I'm trying to associate a Core Spotlight item with an AppEntity during indexing by calling CSSearchableItemAttributeSet.associateAppEntity(_:priority:). However, every time I do so, I get the following warning in the console: {CSInlineDonation[async]: "my.app.bundle.identifier" add-update-items:1 delete-items:0}: Failed to request donation Error Domain=CSIndexErrorDomain Code=-1000 "Failed to request donation" UserInfo={NSDebugDescription=Failed to request donation, NSUnderlyingError=0x143f54ae0 {Error Domain=com.apple.CascadeSets.Set Code=3 "Access denied (<BMResource: set/App.Intents.IndexedEntity [CCSetDescriptor - key: sourceIdentifier value: my.app.bundle.identifier]>)" UserInfo={NSLocalizedDescription=Access denied (<BMResource: set/App.Intents.IndexedEntity [CCSetDescriptor - key: sourceIdentifier value: my.app.bundle.identifier]>), NSUnderlyingError=0x143f54ba0 {Error Domain=BMAccessErrorDomain Code=11 "Failed to prepare resource" UserInfo={NSLocalizedDescription=Failed to prepare resource}}}}} The relevant code is: let attributeSet = CSSearchableItemAttributeSet(contentType: .audiovisualContent) let appEntity = VideoAppEntity(...) attributeSet.associateAppEntity(appEntity) The Spotlight item itself is indexed successfully, but the associateAppEntity call appears to fail with an "Access denied" error related to App.Intents.IndexedEntity. Has anyone encountered this before? Are there additional entitlements, App Intents configuration requirements, or indexing prerequisites needed for associateAppEntity(_:priority:) to work correctly?

iOS 27.0 beta 24A5355q has a completely unacceptable Settings crash that blocks Wi-Fi Calling activation and E911 emergency address setup. This is not some tiny visual bug. This breaks actual phone service. I cannot activate Wi-Fi Calling, I cannot register my 911 emergency address, and my SIM line is effectively unusable because Apple shipped a broken beta Settings app. Process: Preferences / com.apple.Preferences Device: iPhone16,1 Crash type: NSInvalidArgumentException Reason: -[UIThreadSafeNode _smartReplyUpdateInProgress]: unrecognized selector sent to instance The stack points to Apple’s own code: UIPredictionViewController UIKeyboardImpl TextInputUI UIKeyboardLayoutJapanese50OnFlick I tried Bluetooth keyboard, disabling prediction, removing keyboards, rebooting, and avoiding text input. Nothing works. The Wi-Fi Calling / Emergency Address page crashes on load. This is a stupid, critical Apple bug. Settings should never crash when opening a carrier service page, and it is insane that a broken prediction UI can block emergency-address registration and phone service activation. Please fix this immediately, or provide a way to configure Wi-Fi Calling E911 address without loading the broken TextInputUI / prediction UI path.

Does this API only work for inference running on the GPU? If the inference runs on the ANE, can I still use this API? I noticed that the commandQueue parameter is an MTLCommandqueue? https://developer.apple.com/documentation/coreai/computestream/init(commandqueue:)

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.

I have been waiting for the siri ai and doing everything to try to get it, yet I have been stuck on the waitlist since iOS 27 developer beta released, so please help me out🙏

Hi everyone, I joined the new Siri waitlist on Friday at 7:00 PM IST using a new M4 MacBook running the latest macOS 27 Developer Beta (Build 26A5353q). It has now been over 100 total hours (roughly 52 business hours) and my status is still stuck on "Joined Waitlist." My setup is completely clean: System Language and Siri Language are both set to English (US).My storage shows the 27.69 GB Apple Intelligence bundle is already pre-allocated on my SSD. My physical device region is set to India (outside the EU/China geofence). Unified system logs show isOkayToHaveAsset: True and AvailabilityClient.waitlistStatus connections are establishing perfectly with 0% CPU idle on generativeexperiencesd. I have tried clearing the local cache by toggling Siri off/on and performing a full language-flip reboot cycle, but it drops straight back to "Joined Waitlist" without letting me click the join button again (proving the server recognizes my original Friday timestamp). Is anyone else experiencing a massive weekend-backlog server stall on this specific macOS 27 build? How long did your approval take this week?

I have been waiting since last tuesday for the new siri. My primary device, which is my phone is missing and it is out of battery in my home. I don't know where did my phone go. Still, is it possible to get the new siri? I am waiting on my iPad Pro(M1) 2021 model. Also is it my problem that it is taking so long?

Recently about 7 days ago now I have tuned in to the waitlist for the new Beta Siri Ai, I am trying to make tests and review the software on the 16 pro and 17 pro both together to point out key differences and slight changes with the two, I have been waiting for the update. My phone has already finished indexing days ago but unfortunately still no update to the Siri Ai. Some have stated its a bug but theres different reasons on the web and knowing this is a (Beta) and not full on release it makes sense however I wanted to ask you guys personally on your thoughts as I’m still trying to test these out asap. Unfortunately I’m still on the waiting list..

I’ve been on the waitlist for over 9 DAYS since I joined it and it is getting quite frustrating while my friend get access in 2 days. Bro what is this.

Hello Apple community I would like to know why new Siri is currently inactive on my phone. I have a iPhone 17 base model and downloaded iOS 27 beta. I suspect that it is not functioning due to me being 13 and having parental controls on. That is my guess why New Siri is not downloading. The phone states that I have joined the waitlist though my stance on the situation is that there is more to this!

With visionOS 27, if you use a non US Apple ID, if the language is set to English on the country to USA, you don’t get Siri AI even if Siri AI is supposed to be available on visionOS 27 in all countries if the system is in English. iOS and iPadOS are the only systems where Siri AI is not available in Europe. As macOS, visionOS is supposed to have Siri AI enabled worldwide if the system is configured in English. The problem is confirmed with many French Vision Pro users with a French Apple ID. Feedback: FB23207278

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?

My app uses ImageCreator to allow customers to generate images on-device, and provides a custom experience for doing so. I can see that ImageCreator is now being deprecated without a replacement for programatic image generation. Why has the ability to generate images programatically been removed?

Hi Apple Team, I'm trying to use the SkillActivation framework from the Foundation Models Utilities repository: https://github.com/apple/foundation-models-utilities Environment: Xcode 26 Beta iPadOS/macOS 26 Beta Apple Intelligence enabled Foundation Models Utilities: latest version from GitHub Issue: As soon as I import or use SkillActivation-related APIs, Xcode reports build errors and the project fails to compile. The rest of the Foundation Models framework works correctly, but the problem appears specifically when SkillActivation is added. Steps to Reproduce: Create a new project. Add foundation-models-utilities via Swift Package Manager. Import SkillActivation / follow the sample implementation. Build the project. Expected Result: The project should compile successfully and SkillActivation should be available. Actual Result: Xcode reports compilation errors and the build fails. Questions: Is there any additional entitlement, capability, or configuration required for SkillActivation? Is SkillActivation currently supported in Xcode 26 Beta? Are there any known issues with the current version of foundation-models-utilities? Thank you.

Hi there. We use coreml for image processing, and we have many models, each one produces a different effect. However, this error sometimes occurs on some devices. No idea when and how. But once it happens, it keeps failing on the device. At this point, these will solve the issue: Uninstall and reinstall the app. It works fine for a while, but the same error soon occurs again. Reboot the device. It work fine for a longer time than reinstall. I tried repeatedly loading and unloading the model in a loop, but I couldn't reproduce the issue. If the model loads successfully the first time the application starts up, it will continue to load successfully for the remainder of the application's lifecycle. If I repeatedly launch the app, load the model, and then force-close the app—after doing this a few hundred times—the problem will eventually occur. The following are two similar questions: https://developer.apple.com/forums/thread/678599 https://developer.apple.com/forums/thread/740731 A previous reply stated that "it typically means there is a leak in the system," but since the app has already been terminated, the resources it was using should have been automatically reclaimed by the system. This issue has been a problem for a long time; it does indeed appear to be a system-level bug. This uncertainty and unreliability can lead to user churn.

On iOS 27 Beta 1, it looks like the user must enable either "Siri"/"Hey Siri" or "Press Side Button for Siri" in iOS settings for SystemLanguageModel.default.availability to report true. Otherwise, it returns .appleIntelligenceNotEnabled. Is this expected behavior? This doesn't seem very intuitive. The user might very well want to use in-app AI functionalities without wanting to talk / press side button for Siri. Also, with the new "pull down for Siri" UX these are not the only way to interact with Siri anyway.

I am a paid apple developer that has been on the AI waitlist since day one of the keynote. How many other paid developers are still waiting like me?