Environment: macOS 27.0 beta (26A5368g) Xcode 27 beta — Instruments 27.0 (64578.226), build 27A5209h MacBook Pro (M1, 2020), 16 GB — MacBookPro17,1 Target: physical iPhone running an iOS app (on-device LLM inference benchmarking) Summary: Instruments crashes reproducibly with EXC_BREAKPOINT (SIGTRAP) shortly after I stop a recording. Recording itself works — the crash occurs during the post-stop analysis phase, while the trace is being processed. This has happened multiple times today with different templates (Time Profiler, and a custom document with Power Profiler / os_signpost / Thermal State). Steps to reproduce: Open Instruments 27.0 beta, choose Time Profiler (or a document containing Power Profiler + os_signpost) Target a physical iPhone and an installed app Record for a short period, then press Stop Instruments crashes while analyzing/importing the trace Crash details: The crashing thread is always on the dispatch queue com.apple.dt.frame.activity, inside InstrumentsPlugIn transformer/modeler code. In one report the crashing frame is: Thread 10 Crashed:: Dispatch queue: com.apple.dt.frame.activity 0 InstrumentsPlugIn NetworkConnectionStatsModeling.__receiveRow(cursor:writer:referenceManager:) + 920 1 InstrumentsPlugIn TransformerExecutionUnit.run(yieldBlock:) + 92 2 InstrumentsPlugIn specialized TransformerHostingModeler.populateOutputTables(_:usingObserverations:parameters:checkToYieldBlock:) + 2344 Exception Type: EXC_BREAKPOINT (SIGTRAP), esr 0xf2000001 (Breakpoint) brk 1 At crash time, sibling worker threads on the same queue were executing SystemPowerImpactModeling and ProcessSubsystemImpactModeling transformers, so the failure appears to be in the modeling pipeline that runs when the recording is finalized. Incident identifiers from two occurrences today: D6D2467F-8553-487C-A291-EC30C0D2846F (14:13 IST) 55017CAB-5345-4865-9695-36228B B80AA4A (18:20 IST) Filed via Feedback Assistant as FBXXXXXXXX with full crash logs and sysdiagnose attached. Questions: Is this a known issue in the current Instruments 27.0 beta? Is there a recommended workaround to record and analyze traces until a fix ships — e.g., recording headlessly with xctrace and opening the .trace in a late r build? Happy to provide the .trace files or additional diagnostics. Thanks!

Environment • macOS 27 beta 2 • Xcode 27 beta • Apple Silicon Mac Summary After upgrading to macOS 27 beta 2 and Xcode 27 beta, an old iOS 18.5 simulator runtime remains registered internally but cannot be removed. There appears to be an inconsistency between different CoreSimulator commands. Observed Behavior xcrun simctl runtime list only reports the current runtime: == Disk Images == -- iOS -- iOS 26.1 (23B86) - 0753590B-CF3F-4944-899E-4F70698DB87C (Ready) Total Disk Images: 1 (7.8G) However, xcrun simctl list runtimes -j still reports an additional runtime: identifier: com.apple.CoreSimulator.SimRuntime.iOS-18-5 SimulatorVersion: 18.5 Build: 22F77 bundlePath: /Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime runtimeRoot: /Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot The runtime is reported as: "isAvailable": true The runtime no longer appears anywhere in Xcode. Attempting to remove it using the documented command fails: xcrun simctl runtime delete 22F77 Output: No runtime disk images or bundles found matching '22F77'. No matching images found to delete Using the runtime identifier also fails. The corresponding MobileAsset still exists: /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/ It contains: c0d3fd05106683ba0b3680d4d1afec65f098d700.asset Its Info.plist contains: SimulatorVersion = 18.5 Build = 22F77 Another asset exists for the current runtime: SimulatorVersion = 26.1 Build = 23B86 The directory /Library/Developer/CoreSimulator/Volumes/iOS_22F77 exists as an empty directory. It appears to become active only when CoreSimulator queries the runtime. The runtime asset is no longer referenced by /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/com_apple_MobileAsset_iOSSimulatorRuntime.xml Expected Result After upgrading Xcode/macOS: • old runtimes should either be removable through xcrun simctl runtime delete or • they should no longer remain registered if Xcode has already removed them. Actual Result Different CoreSimulator commands report different runtime states. simctl runtime list only reports iOS 26.1. simctl list runtimes -j still reports iOS 18.5 as available. The old runtime cannot be deleted using the official command. The MobileAsset remains on disk and occupies storage, but there appears to be no supported method to remove it. Notes This looks like CoreSimulator's runtime registry and the runtime deletion mechanism have become inconsistent after upgrading to macOS 27 beta 2 and Xcode 27 beta.

If I use the Claude Code agent within Xcode 27 beta 2, it defaults to Opus 4.8, but that burns through tokens too quickly so I'd like to switch it to Opus 4.7 or Sonnet, but there's no way to change that anywhere in Xcode that I can see? Also, if I use Chat, rather than the agent, then Xcode lets you select models, however for Claude it only offers Sonnet 4.5. Why? Why not 4.6 at least? Where are these limitations coming from? It's not from Claude so it must be Xcode Why are these limitations present?

Please help me understand how build SDKs work in Xcode 27. Let's say I have an older app that uses UIDesignRequiresCompatibility. When I a) select an iOS 26 Simulator in Xcode 27 and press "play" (build an run), the app shows up in design compatibility mode. b) select an iOS 27 Simulator in Xcode 27 and press "play" (build an run), the app shows up ignoring design compatibility mode. My questions: Does that mean a) is using iOS 26 as build SDK and b) is using iOS 27 as build SDK? What would happen if running an app built using iOS 26 build SDK on iOS 27? What would happen if running an app built using iOS 27 build SDK on iOS 26? How can 2. and 3. be done with the simulator? When I submit to App Store Connect, which build SDK is used?

We root-caused a launch crash that only affects ARCHIVED builds (Run/Debug works, simulator works) and filed it as FB23528109. Posting the details here because the crash signatures are hard to search for and other teams are likely to hit this as they adopt Swift 6.3 toolchains. SYMPTOM The archived app crashes before main() on device, on every launch. Depending on which orphaned pointer gets read first, the crash looks like one of these: EXC_BREAKPOINT, "pointer authentication trap DA", inside swift_conformsToProtocolMaybeInstantiateSuperclasses / _searchConformancesByMangledTypeName (often with a Firebase or other +load frame below it; that frame is just the first conformance scan at launch, not the cause) EXC_BAD_ACCESS KERN_INVALID_ADDRESS at a small, raw unslid address (e.g. 0xc118), inside dyld: resolveRebase <- objc_visitor::forEachClass <- dyld4::PrebuiltObjC::make Debug builds, simulator builds and Xcode Run builds are all fine, because the corruption happens in the Strip build phase, which only runs for Archive/install builds. ROOT CAUSE (two defects combine) strip -S -T (what Xcode runs on embedded frameworks during Archive when STRIP_SWIFT_SYMBOLS = YES) corrupts dyld chained fixups. When strip removes a Swift weak-definition symbol that has a GOT bind, it converts the bind into a rebase to the local definition (correct) but writes the converted entry with next = 0 (incorrect). That terminates the 16 KB page's fixup chain early, and every fixup after the converted slot in the same page is orphaned: dyld never processes it, so raw chain-encoding bytes get read as pointers at launch. The bug is present in every strip we tested: Xcode 26.3, 26.4, 26.4.1, 26.5, 26.6 and 27.0 beta 2. strip -S and strip -S -x (without -T) do not corrupt. Starting with Swift 6.3.0 (Xcode 26.4.0), the compiler emits the trigger pattern for ordinary code: cross-module references to a non-final class's stored-property accessors become weak-def-coalesce binds (Swift 6.2.4 emits none). So apps that embed a multi-module Swift dynamic framework (e.g. an SPM package built as one dynamic framework) started getting corrupted by their own default Archive pipeline when they moved past Xcode 26.3. HOW TO CHECK IF YOU ARE AFFECTED Compare the fixups of a framework binary inside your archive against a Run build of the same code: xcrun dyld_info -fixups YourApp.app/Frameworks/YourKit.framework/YourKit If fixups that exist in the Run build are missing after the archive's strip step (in particular __got slots and anything after them in the same 16 KB page), you are affected. Also: any GOT bind of a Swift ($s...) symbol in the pre-strip binary is a red flag. WORKAROUND Set STRIP_SWIFT_SYMBOLS = NO (optionally STRIP_STYLE = non-global, i.e. strip -S -x, which kept the size cost to about +4% for us). Important: if the affected framework is a Swift package product, these must be passed as xcodebuild command-line overrides (e.g. xcodebuild ... STRIP_SWIFT_SYMBOLS=NO STRIP_STYLE=non-global); xcconfig files do not apply to package targets. REPRO FB23528109 contains a complete minimal reproducer (4 small C files + 1 trivial Swift file, no proprietary code): a 30-second CLI script whose host binary segfaults through an orphaned pointer, and a default-settings Xcode project whose Run build works while its archived build crashes pre-main on device, identically for archives produced by Xcode 26.3.0, 26.4.0 and 26.6 (crash logs for each attached in the FB). Happy to share more details from the investigation if anyone is debugging the same signatures.

Working with Agents in Xcode 27 is a nightmare right now. Every conversation opens in a new window, so you don't see the code you and the agent are working on. You have to go back and forward between the code file and the conversation tab to get the names of data types or functions you need to ask the agent to work on, or to see exactly what you need to ask or how to explain it to the agent. We need the conversation and the code to be side by side to be able to work on the code and provide the right instructions, as we do in Xcode 26. The current interface just completely ruins any reasonable workflow, unless you are vibe coding, which I don't recommend. Let me know if there is a way to open the conversation on one side and code files on the other, or PLEASE change it back of what it was before or I will have to keep working on Xcode 26 and miss all the new features. Thanks

I'm trying to build an Xcode Cloud workflow, but I keep getting this error. At first it just said I had to accept a license agreement, which I did, but it still didn't work after. I had recently added a new branch to the connected GitHub repository and committed to it so that I can have a beta branch separate from the main one. The only error that happens is when archiving. I am using Xcode 27 beta.

Hi, I'm trying to figure out what is true here - if I am not in the correct forum please direct me :-) A. It is not possible to test a QR code scan that contains a deeplink into my iOS app from an XCoode build test run. In other words, The build must be published to Test Flight for the iOS's QR code scan sub-system to be able to process the deeplink into my app? If I am wrong about this, it sure would help with testing to be able to test directly from the local XCode build test. If so, can someone point me in the direction of what I would need to do for that? Thanks for your input either way!

Im unable to deploy Xcode 27 beta code to an iPhone 17 pro The build is successful but its not loading

I'm trying to build the DriverKit template driver target in an Xcode project which contains an app targeting iPadOS 17. I've made no modifications to the DriverKit template. When building, I get this link error ld: file cannot be open()ed, errno=2 path=/Applications/Xcode 15.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/15.0.0/lib/darwin/libclang_rt.profile_driverkit.a in '/Applications/Xcode 15.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/15.0.0/lib/darwin/libclang_rt.profile_driverkit.a' anyone know how to fix this? My search turned up something about building llvm from sources, which seems like overkill to put a DriverKit driver into an iPad app.

👋🏻 Hello Apple Developer Community, I’ve recently got the problem with the current Xcode Beta Version and the Preview Feature. Because when I try to load the Preview, the RAM Usage spikes and it’s nearly at the limit on my MacBook (16GB RAM). (Note: This is happening while loading up the Preview) But when I haven’t loaded the Preview Window, the overall RAM Usage of my system is ver low (Note: This is when Xcode has is not loading the Preview) (Note: This is after quitting Xcode for cancelling the load of the Preview) All Pictures are in German, sorry for that ☹️. What are possible problems or solutions against this problem? Have a nice day / evening 😁

Hello, Shortcuts and App Intents don't work on simulators running iOS 26 or iOS 27. It's working fine on simulators running iOS 18. It makes testing and adopting new technologies difficult. Please check this feedback which contains a video showcasing the issue with a sample code provided by Apple: FB23342158 Regards, Axel

Dear Apple Developer Support, I am developing and maintaining an iOS application. In iOS 26, we understand that setting UIDesignRequiresCompatibility to true in the Info.plist file allows an app to opt out of the Liquid Glass design. However, we also understand that during WWDC25 Platforms State of the Union, Apple stated: "We intend this option to be removed in the next major release." We would appreciate clarification on the following points. Questions Should the phrase "next major release" be interpreted as iOS 27? Is it currently Apple's plan to make UIDesignRequiresCompatibility unavailable or remove it in iOS 27? Or is the statement above only an intended direction, with the actual removal schedule still subject to change? If there is any publicly shareable information regarding the future availability or deprecation timeline of UIDesignRequiresCompatibility, could you please provide it? Background We develop and maintain a business application that contains a large number of custom screens and UI components. Adapting the entire application to the Liquid Glass design system will require significant design review, implementation effort, and testing. As a result, the future availability of UIDesignRequiresCompatibility is a critical factor in our development planning and resource allocation. For this reason, we would greatly appreciate any guidance you can provide regarding Apple's current plans for this compatibility option. Thank you for your time and assistance. Best regards, Toshiyuki

I signed in to Xcode using my Anthropic credentials. When I attempt to start a new conversation the text box is not enabled and I see a message related to Codex..

Hi all, I have implemented a feature in my iOS application which checks the latest version available on App Store and if there is new update available it shows Pop to update the app. I am using this url for checki https://itunes.apple.com/lookup?bundleId= Issue: For some users this url returns old cached data which is previous version although new version is already live and i have verified this url directly via PostMan or other IDE.

After updating to Xcode 26.5 Xcode crashes when I try to open my project. Directly before update everything was fine... Not using Beta-Software.. only stable versions What can I do? Will there be an update fixing this bug? `Application Specific Information: abort() called Application Specific Signatures: NSInternalInconsistencyException Application Specific Backtrace 0: 0 CoreFoundation 0x0000000186e711c0 __exceptionPreprocess + 176 1 DVTFoundation 0x000000010578a20c DVTFailureHintExceptionPreprocessor + 388 2 libobjc.A.dylib 0x00000001868fa91c objc_exception_throw + 88 3 Foundation 0x000000018868f498 -[NSFileWrapper regularFileContents] + 436 4 IDEStoreKitCore 0x000000030e002b20 $s15IDEStoreKitCore0aB13ConfigurationC4FileV17configurationData10Foundation0G0Vvg + 440 5 IDEStoreKitCore 0x000000030e001da0 $s15IDEStoreKitCore0aB13ConfigurationC13configuration3forACSo13NSFileWrapperC_tKFZ + 304 6 IDEStoreKitCore 0x000000030e003b0c $s15IDEStoreKitCore0aB13ConfigurationC13configuration2atAC10Foundation3URLV_tKFZ + 148 7 IDEStoreKitEditor 0x000000030e792ecc $s17IDEStoreKitEditor0aB20TextFragmentProviderC12generateSeed3for17completionHandlerySo11DVTFilePathC_ySo07IDETextefH0_pSg_s5Error_pSgtctFZ06$sSo27nefh28_pSgSo7NSErrorCSgIeyByy_ABs5o2_pR8Ieggg_TRAJSo0T0CSgIeyByy_Tf1ncn_nTf4ndg_n + 152 8 IDEStoreKitEditor 0x000000030e7922fc $s17IDEStoreKitEditor0aB20TextFragmentProviderC12generateSeed3for17completionHandlerySo11DVTFilePathC_ySo07IDETextefH0_pSg_s5Error_pSgtctFZTo + 52 9 IDEFoundation 0x000000010c922318 __113+[IDETextFragmentIndex runProvider:forFilePath:explicitFileDataType:initialTimestamp:priority:completionHandler:]_block_invoke + 204 10 DVTFoundation 0x00000001058a0638 __51-[DVTThrottledConcurrentQueue processQueueIfNeeded]_block_invoke + 80 11 DVTFoundation 0x0000000105892bd0 DVT_CALLING_CLIENT_BLOCK + 16 12 DVTFoundation 0x0000000105893548 __DVTDispatchAsync_block_invoke + 152 13 libdispatch.dylib 0x0000000186b8aa28 _dispatch_call_block_and_release + 32 14 libdispatch.dylib 0x0000000186ba44b0 _dispatch_client_callout + 16 15 libdispatch.dylib 0x0000000186b8f1c8 _dispatch_continuation_pop + 596 16 libdispatch.dylib 0x0000000186b8e844 _dispatch_async_redirect_invoke + 580 17 libdispatch.dylib 0x0000000186b9c980 _dispatch_root_queue_drain + 360 18 libdispatch.dylib 0x0000000186b9d120 _dispatch_worker_thread2 + 184 19 libsystem_pthread.dylib 0x0000000186d41e84 _pthread_wqthread + 232 20 libsystem_pthread.dylib 0x0000000186d40c10 start_wqthread + 8`

Hello, I’m implementing the AppIntents framework in my app. I want to translate the TypeDisplayRepresentation that is used in the Shortcuts app UI like in a DeleteIntent (see my feedback about this: FB23451186 for more context). In the “Accelerating app interactions with App Intents” sample code we can see that this is done using a .stringsdict file, as follows for the “Trail” key (singular and plural): <key>Trail</key> <dict> <key>NSStringLocalizedFormatKey</key> <string>%#@VARIABLE@</string> <key>VARIABLE</key> <dict> <key>NSStringFormatSpecTypeKey</key> <string>NSStringPluralRuleType</string> <key>one</key> <string>Trail</string> <key>other</key> <string>Trails</string> </dict> </dict> I want to use a String catalog instead of a .stringsdict file because all my strings are in a String catalog. I tried to migrate the AppIntents.stringsdict file manually but it failed with an error: “An error occurred when migrating AppIntentsSampleApp/Resources/AppIntents.stringsdict: This stringsdict cannot be migrated: Missing required key 'NSStringFormatValueTypeKey' inside 'Trail' -> 'VARIABLE’” So I manually added a NSStringFormatValueTypeKey like this in the .stringsdict file: <key>Trail</key> <dict> <key>NSStringLocalizedFormatKey</key> <string>%#@VARIABLE@</string> <key>VARIABLE</key> <dict> <key>NSStringFormatSpecTypeKey</key> <string>NSStringPluralRuleType</string> <key>NSStringFormatValueTypeKey</key> <string>lld</string> <key>one</key> <string>Trail</string> <key>other</key> <string>Trails</string> </dict> </dict> And then I’ve been able to migrate the .stringsdict file into a String catalog. The string catalog looks like this after migration: "Trail" : { "extractionState" : "stale", "localizations" : { "en" : { "stringUnit" : { "state" : "translated", "value" : "%#@VARIABLE@" }, "substitutions" : { "VARIABLE" : { "formatSpecifier" : "lld", "variations" : { "plural" : { "one" : { "stringUnit" : { "state" : "translated", "value" : "Trail (Catalog)" } }, "other" : { "stringUnit" : { "state" : "translated", "value" : "Trails (Catalog)" } } } } } } } } This works, which is nice. But I tried to reproduce the same result by having a %#@VARIABLE@ in my LocalizedStringResource defaultValue like this: TypeDisplayRepresentation( name: LocalizedStringResource( "Flower", defaultValue: "%#@VARIABLE@", table: "AppIntents" ), numericFormat: LocalizedStringResource( "\(placeholder: .int) flower", table: "AppIntents" ) ) But the String catalog doesn’t support that apparently, I can’t get a “substitution” object in my catalog, so I have to manually do it using the source code which is not ideal and painful. Is there a way to support this kind of substitution with no actual plural token in the string as we can see for the %#@VARIABLE@ for Trail? Thank you, Regards, Axel

In Xcode project > Build Settings > Swift Compiler - Concurrency. When we have those settings : Approachable Concurrency - Yes Default Actor Isolation - MainActor A sendable struct without @Actor annotation will be stuck to @MainActor. But if we have a sendable struct, by principle, it should be used across Actors. To remediate the situation, we had to prefix the struct with nonisolated keyword. The setting "Default Actor Isolation - MainActor" should not add @MainActor to Sendables. Problem describe in : FB23264607

I'm trying out Xcode 12 (beta) and encountered an issue with TextField when viewing it in a live Preview. Although the view is interactive (scrolling vertically seems to be OK) and a cursor appears in the TextField view when it is clicked on, keyboard input is ignored. The same code works as expected in Xcode 11.5. Simulator in both 11.5 and 12 exhibits expected behaviour. Is this a bug? I know there is an issue with interactivity in Preview with multiple views inside PreviewProvider but I'd assumed this is if you'd added multiple Views to the same body of this struct.

AI agentic coding is great, but it drifts away from the good practices and good code. Sometimes I am writing code while thinking what exactly to write, exploring the architecture solution, the data flow, not the technology, so making a prompt is not the best use case. I am doing iOS development in VSCode since preview version of Copilot launched, the auto-completions that AI provides IS the greatest tool a developer can have Please 🙏 prioritize the unimaginable good auto-completion that only Apple can provide, so that we can auto-complete function implementation, class implementation, multiple lines of comments in a fraction of a second