I'm seeing auth failures when attempting CloudKit operations: "Account Temporarily Unavailable" (36/1028); "Account temporarily unavailable due to bad or missing auth token" I see this for Modify zone operations, Modify records, and zone changes too. Everything. Only started happening after updating to iOS 15 beta 4 and Xcode 13 beta 4. Account status is "available".

I'm seeing a lot of unexpected CPU usage when running the iOS 26.1 simulator. Looks like a "MercuryPosterExtension" is crashing over and over, which then causes the "ReportCrash" process to run, presumably to create the crash report. Doesn't happen on device, nor on iOS 26.0 simulator. I suspect MercuryPoster is related to wallpaper. I also don't see any wallpaper background in my simulator. Few lines from the stack trace: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libxpc.dylib 0x18011defc _xpc_api_misuse + 88 1 libxpc.dylib 0x18012e16c _xpc_shmem_create_with_prot.cold.1 + 24 2 libxpc.dylib 0x180113a70 _xpc_shmem_create_with_prot + 276 3 MTLSimDriver 0x23795ed48 -[MTLSimDevice newBufferWithLength:options:pointer:copyBytes:deallocator:] + 260 4 MercuryPosterExtension 0x10081d21c 0x100758000 + 807452 13 PosterKit 0x240d003d8 -[PRRenderer scene:willConnectToSession:options:] + 648 14 UIKitCore 0x1856bcf18 +[UIScene _sceneForFBSScene:create:withSession:connectionOptions:] + 956

The speaker mentions there is "less risk of creating a retain cycle in when capturing self in a closure within a value type", such as a SwiftUI view struct. Can you elaborate on when this could actually occur? Thanks!

I'm building and running from Xcode 26 to macOS 15.5. On launch, app crashes on start dynamic runtime linking with failure to find _LocationEssentials framework.

For example: I have a list of to-dos, each with a unique id (a GUID). I want to feed them to the LLM model and have the model rewrite the items so they start with an action verb. I'd like to get them back and identify which rewritten item corresponds to which original item. I obviously can't compare the text, as it has changed. I've tried passing the original GUIDs in with each to-do, but the extra GUID characters pollutes the input and confuses the model. I've tried numbering them in order and adding an originalSortOrder field to my generable type, but it doesn't work reliably. Any suggestions? I could do them one at a time, but I also have a use case where I'm asking for them to be organized in sections, and while I've instructed the model not to rename anything, it still happens. It's just all very nondeterministic.

Getting the following warning on submission: ITMS-90626: Invalid Siri Support - Localized title for custom intent: '---' not found for locale: ... We get a similar warning for Localized description: : Invalid Siri Support - Localized description for custom intent: '---' not found for locale: ... Binary is accepted but would like to stop the warning. This is an intent used for the dynamic configuration of widgets. It is its own Siri extension target which contains the intent definition file. The intent definition is localized correctly (the intent presents one user facing string on the back of the widget that appears correctly in different locales). In the widget case, the title and description are never visible to the user. That's more for other uses of intents, like Shortcuts. "Account" is the user-facing string and it localizes correctly. I assume the title and description strings the warning mentions are the ones listed in the intent definition file (which are also localized). Thanks for any help!

Submitted a build for iOS 15 and app was rejected with the following message. Is there something special we need to do when submitting early for iOS 15 using Xcode 13 RC? Could it be that I selected "Release immediately?" I expected that to actually release immediately on the 20th?? Your app or its metadata contains references to a pre-release version of Apple software, products, or hardware. Apps with compatibility references to a pre-GM version of an Apple operating system SDK or pre-released Apple products or hardware are not in compliance with the Apple Developer Program License Agreement. Specifically, section 2.3 states: "Apple may provide You with pre-release versions of the Apple Software or related services that constitute Apple Confidential Information and are subject to the confidentiality obligations of this Agreement." Next Steps Please remove all references to pre-release versions of Apple software, products, and hardware from your app and its metadata.