I'm developing an iOS app that uses imagePlaygroundSheet to generate images based on AI-generated prompts (not user-typed text). I would like to confirm whether the following usage is permitted under the Apple Developer Program License Agreement: Generate an image using imagePlaygroundSheet within my app Pass the resulting image (obtained via the completion handler URL) as an input to a third-party video generation API (e.g., to create an image-to-video animation) Offer this video generation as a paid feature (consumable in-app purchase) within my app I've reviewed Section 3.2(8) of the ADPLA, which prohibits using "output generated from an Apple model to train, fine-tune, or improve another artificial intelligence model." My understanding is that this clause is specifically about training/improving AI models, not about using the output image as a content input for a separate processing step (e.g., animation). Could someone confirm: Whether passing imagePlaygroundSheet output to a third-party API for further processing (not training) is permitted Whether monetizing a feature that uses this combined output is permitted Thank you in advance for any guidance.

I’m on a base iPhone 17 and I‘ve been approved from the waitlist over two weeks ago and when I use Siri, I get the old Siri from before Apple Intelligence was a thing (Glowy orb at the bottom). Inside Siri settings, it looks like it’s supposed to be set up for the new SirI as it shows the app settings. Here are my observations I have found from using beta 1 to 2. Beta 1: Whenever I have the new Siri “enabled”, there is no app I can type “siri://“ and it‘ll open the Siri open saying that’s there’s an update in progress. But if I type that in when I’m using the previous Siri, the app is there and it’s blank When new Siri is ”enabled” and whenever I ask Siri a question she’ll either think and never stop or output a blank answer. But when I turn Siri back to its previous version and open the “sir://“, it stores the conversation and when I open it, it actually answered my question. Beta 2: When installing beta 2 I said “new Siri“ enabled Once it was done installing, I went to iPhone storage and saw that “Apple Intelligence“ storage is increasing size. But then after a minute, it went back down to 14GB Still gave me the old Siri UI Now the siri app is not accessible when typing “siri://“ Siri mode is now in the camera app but it says it’s unavailable The ChatGPT extension area is now blocked because assets are downloading Whenever I visual intelligence and press ask it says that siri support is downloading I left siri alone for 3 days and nothing happened. Still stuck with old siri The ask siri option is everywhere now and when I press it, nothing happens Right now I’m using the previous version of Siri and hoping this bug will be patched and I can use the new Siri AI in Beta 3. *the screenshot provided shows what happens when I use Siri in beta 2 when it’s enabled.

In the WWDC 2026 sessions it was called out in code that the helper functions would still work, however they don't seem to be working either inside a UIViewRepresentable, nor as a UIKit View as below (also tried as a sheet, to no avail). Otherwise it works. Is there something else I'm missing? import SwiftUI import ImagePlayground @available(iOS 27.0, *) final class ImagePlaygroundPopupController: UIViewController { var sourceImage: UIImage var prompt: String var onComplete: (URL) -> Void var onCancel: () -> Void private var didPresent = false private var playgroundVC: ImagePlaygroundViewController? init( sourceImage: UIImage, prompt: String, onComplete: @escaping (URL) -> Void, onCancel: @escaping () -> Void ) { self.sourceImage = sourceImage self.prompt = prompt self.onComplete = onComplete self.onCancel = onCancel super.init(nibName: nil, bundle: nil) view.backgroundColor = .clear } required init?(coder: NSCoder) { fatalError("init(coder:) has not been implemented") } override func viewDidAppear(_ animated: Bool) { super.viewDidAppear(animated) guard !didPresent else { return } didPresent = true let vc = ImagePlaygroundViewController() vc.sourceImage = sourceImage vc.concepts = [.text(prompt)] vc.delegate = self playgroundVC = vc present(vc, animated: true) } } @available(iOS 27.0, *) extension ImagePlaygroundPopupController: ImagePlaygroundViewController.Delegate { func imagePlaygroundViewController( _ imagePlaygroundViewController: ImagePlaygroundViewController, didCreateImageAt imageURL: URL ) { imagePlaygroundViewController.dismiss(animated: true) { self.playgroundVC = nil self.onComplete(imageURL) } } func imagePlaygroundViewControllerDidCancel( _ imagePlaygroundViewController: ImagePlaygroundViewController ) { imagePlaygroundViewController.dismiss(animated: true) { self.playgroundVC = nil self.onCancel() } } } @available(iOS 27.0, *) struct ImagePlaygroundPopupView: UIViewControllerRepresentable { let sourceImage: UIImage let prompt: String let onComplete: (URL) -> Void let onCancel: () -> Void func makeUIViewController(context: Context) -> ImagePlaygroundPopupController { ImagePlaygroundPopupController( sourceImage: sourceImage, prompt: prompt, onComplete: onComplete, onCancel: onCancel ) } func updateUIViewController( _ uiViewController: ImagePlaygroundPopupController, context: Context ) {} }

still no sign of the new siri no app no nothing im on the ios 27 beta 2 and iphone 15 pro max what is this apple

Actually trick to change language to English UK, restart and change back to English US worked for me. After this in an hour notification showed up and Siri AI was ready.

I live in Canada and I called apple support, they said the new Siri ai isn’t available in some parts of Canada. I’ve changed my region to united states and now it’s just a waiting game. If i now get it fast and quick I’ll let u guys know

I’m going on 2 1/2 days waiting on the indexing and still on the wait list is there something I am missing or should I just wait it out

I found a UI/error-handling issue involving Siri AI where a raw/internal-looking error code is shown directly to the user instead of a user-friendly message. Environment: Device: iPad Pro 11-inch (M4) iOS/iPadOS version: 27.0 Siri / Apple Intelligence enabled: Yes App involved: Files & PDF Expert UI/context: Siri AI interaction with a document from Files File type: .doc Observed behavior: I asked Siri AI to create a new note inside a document through the app integration. Instead of completing the request or showing a user-friendly failure message, iOS displayed this raw error notification: “From PDF Expert: The operation couldn’t be completed. (TypedValueToContentGraphResolutionErrorDomain error 4.)” Expected behavior: Siri AI should handle this failure gracefully and explain that it could not create a new note in the document, instead of exposing the raw error domain and error code to the user. Screenshot:

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?

Dears, I have reached out to Apple Research and Apple Security but this is NOT really for them. This is a developer topic !! Apple Research and Security are trying to find a malicious code, bugs ect, but what I am whitnessing is different and much much deeper into the code. Apple Intelligence in Slovakia is much more limited then in other countries. A specific security configuration due to EU regulations in combination with Siri NOT able to speak or understand Slovak. At low level this combination with a small PUSH with good timing, makes the devices to completely strip themselves off, of all security and trust certifications. What follows is a blank completely from scratch processed reinstall, where the attacker only prepares the "CORRECT" files and information and all the work is done by Apple system itself !!! The result is a complete domination of hardware using the NPU (ANE) chip, which does all the job. And I mean each pixel, sound, connection ect... What is the MOST ALARMING is that due to the proud declaration of customer data privacy this is the exact spot where if something like this happens, Apple will NOT be able to see it. The Customer is then in an extreme situation, where he knows that the devices, accounts, keychain, bank account, each app, each picture or sound.... Everything is compromised, but online help and the retailers are too short for this and further to this Apple DONT HAVE AN OFFICE in Slovakia. Only thing left are the contracted service (repair) shops, which are capable to perform a DFU Restore, which does NOT help. I have requested DFU Restore approx 15x in the last 9 months. Once you turn on and you only pick the language, there is a GLITCH and you know this is back again. A very quick and not too detailed process: It is a very silent and extremely sophisticated takeover without an ovious crash at the beginning. Using various tools, which I can describe and present examples. One variation is a HTML code a DOM which is recursive, calling functions and cancelling. Too many functions with offset which results in a graphics freeze, overload or similiar.. The object itself is not frozen and it is carefully prepared !! It will mostly copy and clone the target and NEST inside without knowing. What happens here is that this recursive DOM was applied and therefore the SHUTDOWN MONITOR LOG occured. This froze also mds index which blocked the mounting and unmounting of Volumes.... This is ofcourse carefully instrumented not to raise any attention. Same structure can be used in any code, any language, pdf, it can be nested in a wallpaper or a standard image, library, anywhere ... I can provide a proof and a functional script... The install log is showing - Untracked client connected - RemoteManagement which REINSTALLED the OS. After that Launchd skipps almost all tasks on the next run .... After this mounting volumes block, the system will not restart as standard, insted forced to early boot as possible which starts with PKI TRUST and SIRI UNDERSTANDING ... The PKI TRUST is manipulated and prepared and Siri is not called by the system as Apple Inteligence. So with reinstalled and carefully prepared OS, Launchd who skipped most tasks at the start and without proper encryption. There is a direct open path to Siri and her ASR HAMMERING.... I have personally checked almost 10 different electronics shops and checked the console on each Macbook that was free to try. In each of them these four Protolol logs were the exact same !!!! But after that a brutal iphone reinstall and even over lockdown mode reinstall will follow... Can also provide logs and information... And there is a SIMPLE LOGIC PARADOX with HUGE impact. Any document can be signed by Apple in a second. That is how the PKI TRUST was manipulated without any problem. That is also extremely important ... I can present this, but I must know that somebody is listening.... otherwise the only way is press... Apple Research and Security is blind here and I simply cannot get any answer.... If you know anybody in Slovakia, tell them to go to check this out !!! Get this information to Somebody who could just check it please .... This is probably the largest Supply Chain Attack ever ... And all it takes is a phone call to iStores to Slovakia so they can check for you ... From what I can see, now an update is prepared for Siri. It is based on Ruby but mostly Nokogiri and Gumbo. It will be presented as a 8 bit range training for local LLM, as super fast, but really it will be a combination of Hohner Electric Piano from the 70s with 8 bit sound which will use DTrace and its ROOT privileges. The sound is a square frequency which can be used to hide communication or something we dont know yet. And it does not matter anymore... With a direct connection to GitHub or just the internet ... Any code can be signed and stored anywhere .... The codename is ELECTRA, from what I know this tag was used for jailbreak of Siri in the past. So I belive this will be the final act ... Is there somebody to whom I can speak to about this ?? No generic mails ... THX Mike

I don’t even see the waitlist of the Apple Intelligence program, i think it’s lacking instruction’s how to apply, when it comes out etc.

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.

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

Hi everyone, I’m testing the latest iOS 27 beta and I’ve noticed an issue with the new Siri. When I ask very simple questions that should be handled locally or through basic reasoning, Siri consistently responds with: “Uh oh, something went wrong.” For example, asking: “When is the next Friday the 13th?” results in the error message instead of an answer. I’ve reproduced this multiple times and it seems to happen with other straightforward informational queries as well. I’ve already tried restarting the device and checking my network connection, but the issue persists. Has anyone else experienced this behavior with the new Siri in the iOS 27 beta? If so, were you able to find a workaround or identify what’s causing it? Any help or confirmation would be greatly appreciated. Thanks!

I finally installed iPadOS 27 developer beta 1 on my iPad Air (M2), opened Settings app and went to the Siri section. There’s no option to join a waitlist. I had Apple Intelligence enabled on iPadOS 26, but in 27, the “Apple Intelligence & Siri” section simply reads “Siri” now. No mention of Apple Intelligence at all! Has anyone else encountered this? Is it a regional thing? I’m in Canada. EDIT: Ok it was a region thing. I changed my region to US and the waitlist option appeared.

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.

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!

I can't figure how to install it Here's google post: You can use the following free options directly inside Xcode 27:1. Built-in On-Device Predictive Code CompletionApple provides a free on-device, on-chip model that runs entirely locally on your Mac.Cost: 100% Free (no internet connection or subscription required).How it works: It uses Apple Silicon to predict and autocomplete your Swift code instantly as you type.Setup: Go to Xcode > Settings > Intelligence and ensure local code completion is toggled on.2. Free-Tier Cloud Models (ChatGPT, Claude, & Gemini)Xcode 27 explicitly features a native two-tier intelligence system. For simple completions, it uses your local chip. For complex planning, multi-turn conversations, and writing autonomous unit tests, it integrates directly with cloud providers. You can utilize the free tiers of these services:Anthropic Claude: You can generate a free API key from the Anthropic Developer Console to power Xcode 27’s coding agents.OpenAI ChatGPT: You can hook Xcode directly into OpenAI's free-tier API allowance.Google Gemini: Xcode 27 natively supports Google's ecosystem, allowing you to use a free Gemini API key.Setup: Navigate to Xcode > Settings > Intelligence, select your cloud provider, and paste your free API key.3. Fully Local Open-Weight Models via OllamaIf you want to handle complex agent tasks without data leaving your Mac, you can connect Xcode 27 to local open-source models. This requires an Apple Silicon Mac.Recommended Models: qwen2.5-coder (highly recommended for Swift and SwiftUI) or llama3-coder.Setup:Download and run Ollama.Pull the model via your Mac terminal (ollama run qwen2.5-coder).Use an Xcode 27 compatible local-host bridge tool or local API endpoint under the "Custom Provider" option in Xcode's Intelligence settings to link Ollama's local port (localhost:11434) straight into your workspace.Xcode 27 Agent SkillsWhen using these models in Xcode 27, they will automatically ingest Apple's native Agent Skills (like the SwiftUI Specialist Skill). This means even a generic free model will receive Apple's optimized context rules to write better, modern Swift 6 code.Are you looking to use the model mostly for inline code autocompletion or for the new conversational agent features (like having the AI autonomously write tests and fix bugs in your workspace)? I can walk you through the exact setup steps for either.19 sitesXcode 27 Beta Release Notes | Apple Developer DocumentationOverview. Xcode 27 beta includes Swift 6.4 and SDKs for iOS 27, iPadOS 27, tvOS 27, macOS 27, and visionOS 27. Xcode 27 beta suppo...Apple DeveloperInside Apple Intelligence and Xcode: Special Presentation | WWDC26so today we're going to build something fun live on stage together but first can we'll give you a quick tour of Xcode. 27. all rig...49sYouTube·Apple DeveloperSwiftUI Best Practices, straight from Apple's Xcode 27 Agent SkillSwiftUI Best Practices, straight from Apple's Xcode 27 Agent Skill. Xcode 27 launched during WWDC 2026 and includes Apple's SwiftU...SwiftLeeShow all

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.