Hi, I'm trying to run our StoreKit unit tests with Xcode26.5 on an iOS26.5 simulator. Host computer has macOS26.5. All tests are failing and in the console I see logs such as [SKTestSession] Error saving configuration file: Error Domain=SKInternalErrorDomain Code=3 "(null)" [SKTestSession] Error deleting all transactions: Error Domain=SKInternalErrorDomain Code=3 "(null)" [SKTestSession] Error clearing overrides: Error Domain=SKInternalErrorDomain Code=3 "(null)" [SKTestSession] Error setting value to 1 for identifier 2 for jp.unext.mediaplayer: Error Domain=SKInternalErrorDomain Code=3 "(null)" And the simulator asks me to provide my AppleID. Tests have been broken since at least 26.4 The release notes claims that it has been fixed but not for me. https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-26_5-release-notes#StoreKit-Testing-in-Xcode Does anyone else have the same issue? Reported FB22774836 just in case.

Apple M1 Pro, 26.5.1 (25F80) XCode 27.0 Beta (27A5194q) Command Line tools for Xcode 27 are installed. Device Hub Version 27.0 (235.4.2) Within device hub I can not create iOS 27 simulators. Only the 26.5 simulators are listed there. I installed the iOS 27.0 SDK. Also deleted and reinstalled it. The computer was restarted. No change. I am unable to create the proper iOS 27 Simulators. Any idea why this is not working? Thanks for the help upfront.

I’m attempting to set up Gemini agentic support in Xcode 26.6 RC (and I'm assuming the process is the same in 27), but since I need to use Gemini with a corporate account, I have a Google Cloud Project ID, not an API key, so it seems like the configuration file route is the right path? After consulting Gemini and filling out the .env file and settings.json files, Xcode is complaining about needing to be authenticated, and I can’t seem to see how to trigger the auth, like one might do in Gemini CLI. I'd appreciate any suggestions or advice at this point. Thanks in advance!

iOS simulator downloads loads of data even over personal hotspots that should be low data - 10s of GBs which exhausts cellular plans. I.e. I'm connecting the phone over USB (charging and it automatically shares the cellular connection and faster deploy and debugging). I see that /Library/Developer/CoreSimulator/Volumes/iOS_23F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.5.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/nsurlsessiond downloads 10s of GBs probably in /Library/Developer/Xcode/UserData/Previews/Simulator Devices/<UUID>/data/private/var/MobileAsset/AssetsV2 over time. Most plans are not that infinite. Has anyone seen such thing? The phone is connected over USB and automatically used as network device and also has the low data mode toggle on.

what can i do?

Hi, I have been testing Xcode 27 beta 2 on macOS 27 beta 2 on a MacBook Air M2 (base model) with 16 GB of memory. When loading previews for the first time, it could take a while, but it looks significantly longer compared to Xcode 26.x on macOS 26.x. Then when trying to launch a simple app with a few screens, the Device Hub takes forever, and then on Activity Monitor, the swap used starts to climb up, almost as high as 12 GB or more. Running an app on Device Hub is almost impossible. Is this a limit of what a MacBook Air can do? This is not my primary machine by the way.

I was hoping this was fixed in Beta 2, but I am having the same issue. I run my app: on a simulator device Device Hub opens Begins installing the app I see the icon and it starts to fill in The launch screen loads and never finishes loading. I then stop running app in Xcode. Device Hub still shows launch screen I restart device in Device Hub I then can open the app and test Anyone else experiencing this? I would really like to solve this as it makes testing changes a frustrating experience. Because I then have to close Device Hub and Xcode to simulate again.

ChatGPT stopped working in Xcode MacBook Air M2 2022 MacOS 26.5.1 Xcode 26.5 ExpressVPN Version 11.71.0 (90727) Internet connection is working fine. On late night June 22, ChatGPT in Xcode was working fine. Then I started getting “cannot complete” messages with “network error”. Now ChatGPT in Xcode does not work at all. My subscription to ChatGPT auto-renewed on June 23. My bank confirms that the payment went through. I logged into ChatGPT in Safari and Firefox. The account looks fine. In Xcode settings/Intelligence/ChatGPT in Xcode, the Usage Limit says Under Limit. I signed out of ChatGPT from within Xcode, and signed back in. It still is not working. I quit and restarted Xcode, then signed out of ChatGPT again, and signed back in. Still not working. Restarted my Mac, opened Xcode. It still doesn’t work. Signed out and back into ChatGPT in Xcode. ChatGPT still is dead. Disabled VPN. Quit and restarted Xcode. ChatGPT still not working. 1-800-ChatGPT was no help at all. I can use ChatGPT while logged into my account on their website. I told it “ChatGPT in Xcode has stopped working”. It came back with: “I’ll help narrow this down. I’ll check current official OpenAI guidance/status first, then give you the fastest troubleshooting path for Xcode specifically. Thought for 6s Try this order: 1 Update ChatGPT for macOS — Work with Apps/Xcode needs ChatGPT macOS 1.2025.057 or later. 2 Restart both apps: quit ChatGPT and Xcode completely, then reopen Xcode first, ChatGPT second. 3 In ChatGPT macOS, check Work with Apps is enabled and Xcode is selected/available. 4 macOS permissions: System Settings → Privacy & Security → Accessibility and Automation. Make sure ChatGPT is allowed to control/read Xcode. 5 In Xcode, open an actual source file and put focus in the editor, then try ChatGPT again. 6 Check OpenAI status; current status page shows ChatGPT service status and incidents. 7 If on corporate/VPN network, try off VPN; OpenAI notes TLS/SSL inspection can break app access. Most common fix: update ChatGPT macOS + re-grant Accessibility/Automation permissions.” I never had the app ChatGPT for MacOS. I set up an account on ChatGPT.com and enabled it in Xcode. That was working fine until the June 23. ChatGPT is not in System Settings → Privacy & Security → Accessibility. Downloaded ChatGPT for MacOS. Quit Xcode. Added ChatGPT to. System Settings → Privacy & Security → Accessibility. Started ChatGPT. Started Xcode. Signed out of ChatGPT in Xcode, and signed back in. ChatGPT in Xcode still is dead. I am at a complete loss. Can anyone help? Doug

Hi, I'm having a strange issue with my new MacBook Pro M5. My iPhone 17 is connected via USB. The phone appears in Finder, so the Mac clearly detects it, and I can access it there. However, the Xcode doesn't see the iPhone at all. Both the MacBook Pro and the iPhone are running version 26.5. What's confusing is that the exact same iPhone and the exact same USB cable work perfectly with my older Intel-based MacBook Pro. Has anyone else experienced this, or have any suggestions on what I should check?

I wonder is anyone at Apple still using Interface Builder for anything… Across Xcode 16.x and 26.x, IB has become increasingly and noticeably slower to open storyboard and xibs. I see zero improvements in Xcode 27 beta. This morning I had both 26 and 27 going fairly quickly into "application not responding" state when trying to render a rather simple layout in storyboard. What's making it worse is that force-quitting the app and starting again leads straight back into the same storyboard and then locks up again. It does not matter if I manage to switch to a .swift file — it's clearly still doing something in the background related to that storyboard and gets stuck. I eventually managed to open just the .storyboard (without the project), fix the offending layout bits and now it's at least not getting stuck although it still takes good 5-6s before it renders a layout with about a dozen components. I assume something with LLM agents is the reason for this issue but come on people — this is infuriatingly incapacitating tool for people like me that are still maintaining UIKit apps.

When running a mobile app through Xcode, why can't the associated watch app be installed within the watch app? How can this problem be solved?

I've created a basic Multiplatform Project in Xcode, by going to File > New > Project. I've also included the default widget extension target. When I run the widget on Mac, and I control-click and choose "Edit Widget" the widget just kinda turns gray and floats over other windows, but does not let me configure anything. We leave the option to use configure with app intents turned on when adding the widget extension target. When I run the same project on an iPhone simulator, I can configure the widget without any issue. If someone else has a few minutes, can they see if this repeats for them? We are running this test because we are seeing the same experience in a real widget we are trying to develop but we can't get it to go into configuration mode on Mac.

I can not seem to get ll the pieces working here. Has anyone set up grok? URL - https://api.x.ai/v1/chat/completions api-key ---- API Key Header x-api-key Doesn't work. Any help would be greatly appreciated. Thanks, Rob

Title: Xcode 27 beta 27A5194q: aimodelc reports “Core AI requires the Metal Toolchain” although Metal Toolchain is installed Description: I am trying to compile a Core AI asset using Xcode 27 beta on macOS 27. CoreAI.framework is available and the Metal Toolchain component is installed, but aimodelc refuses to compile with: error: Core AI requires the Metal Toolchain. note: Download it from Xcode > Settings > Components > Other Components. Environment: macOS 27 beta Xcode 27.0 beta Xcode build: 27A5194q Metal Toolchain installed build: 27A5194o Apple Silicon Mac Diagnostics: xcodebuild -version reports: Xcode 27.0 Build version 27A5194q xcodebuild -showComponent MetalToolchain -json reports: { "buildVersion": "27A5194o", "status": "installed", "toolchainIdentifier": "com.apple.dt.toolchain.Metal.32023.917", "toolchainSearchPath": "/private/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v27.1.5194.15.4aqDVJ" } The actual tools resolve: xcrun --find aimodelc /Applications/Xcode-beta.app/Contents/Developer/usr/bin/aimodelc xcrun --find coreai-build /var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v27.1.5194.15.4aqDVJ/Metal.xctoolchain/usr/bin/coreai-build xcrun --find metallib /var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v27.1.5194.15.4aqDVJ/Metal.xctoolchain/usr/bin/metallib Reproduction: Install Xcode 27 beta build 27A5194q. Install Metal Toolchain from Xcode > Settings > Components > Other Components. Confirm xcodebuild -showComponent MetalToolchain -json reports Metal Toolchain installed. Attempt to compile a Core ML package to Core AI: xcrun aimodelc compile --output /private/tmp/vesta-coreai-smoke/ManualPatchCheck.coreai /private/tmp/vesta-coreai-smoke/AFM27CoreAISmoke.mlpackage Actual result: aimodelc fails immediately: error: Core AI requires the Metal Toolchain. note: Download it from Xcode > Settings > Components > Other Components. Expected result: aimodelc should recognize the installed Metal Toolchain and compile the Core AI asset, or Xcode should provide a Metal Toolchain component compatible with Xcode build 27A5194q. Additional details: Running: xcodebuild -downloadComponent MetalToolchain downloads and installs Metal Toolchain 27A5194o. Running: xcodebuild -downloadComponent MetalToolchain -buildVersion 27A5194q fails with: xcodebuild: error: Failed fetching catalog for assetType (com.apple.MobileAsset.MetalToolchain), serverParameters ({ RequestedBuild = 27A5194q; }) This suggests Apple’s component catalog currently provides Metal Toolchain 27A5194o while Xcode is build 27A5194q, and aimodelc does not accept this installed component as compatible. Please confirm whether Metal Toolchain 27A5194o is intended to work with Xcode 27A5194q. If not, please publish the matching Metal Toolchain component or adjust aimodelc/component compatibility detection.

I am receiving this error when uploading to AppStore Connect: Validation failed This bundle Payload/Document IT.app/Frameworks/iOSAppSDK.framework is invalid. The Info.plist file is missing the required key: CFBundleVersion. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion (ID: b4774d8b-1f34-4c18-90d9-d47a76d3c3dd) My PLIST in Xcode appears to be correct, and my Build Settings appear to be correct. Any ideas why I am seeing this issue? I uploaded a version for the iPhone that uploaded correctly.

I can't use cloud-based AI providers, so I'm very excited about the potential of local models with Xcode's Coding Assistant. I've been playing around with a local MLX model, and have been generally pretty satisfied with it. But I'm curious - what features am I missing out on by using a local model instead of a larger, cloud-based model? Is Xcode's ability to run tests, build the project, etc. limited by the use of a local model? Does it limit the ability to do more complex agentic workflows? If so, how? Basically, local models in Xcode seem to be working pretty well for me, and I'm curious to know what cloud-based models can offer that I don't already have.

Description I've encountered a consistent hang/freeze issue in SwiftUI applications when using nested LazyVStack containers with Accessibility Inspector (simulator) or VoiceOver (physical device) enabled. The application becomes completely unresponsive and must be force-quit. Importantly, this hang occurs in a minimal SwiftUI project with no third-party dependencies, suggesting this is a framework-level issue with the interaction between SwiftUI's lazy view lifecycle and the accessibility system. Reproduction Steps I've created a minimal reproduction project available here: https://github.com/pendo-io/SwiftUI_Hang_Reproduction To Reproduce: Create a SwiftUI view with the following nested LazyVStack structure: struct NestedLazyVStackView: View { @State private var outerSections: [Int] = [] @State private var innerRows: [Int: [Int]] = [:] var body: some View { ScrollView { LazyVStack(alignment: .leading, spacing: 24) { ForEach(outerSections, id: \.self) { section in VStack(alignment: .leading, spacing: 8) { Text("Section #\(section)") // Nested LazyVStack LazyVStack(alignment: .leading, spacing: 2) { ForEach(innerRows[section] ?? [], id: \.self) { row in Text("Section #\(section) - Row #\(row)") .onAppear { // Load more data when row appears loadMoreInner(section: section) } } } } .onAppear { // Load more sections when section appears loadMoreOuter() } } } } } } Enable Accessibility Inspector in iOS Simulator: Xcode → Open Developer Tool → Accessibility Inspector Select your running simulator Enable Inspection mode (eye icon) Navigate to the view and start scrolling Result: The application hangs and becomes unresponsive within a few seconds of scrolling Expected Behavior The application should remain responsive when Accessibility Inspector or VoiceOver is enabled, allowing users to scroll through nested lazy containers without freezing. Actual Behavior The application freezes/hangs completely CPU usage may spike The app must be force-quit to recover The hang occurs consistently and is reproducible Workaround 1: Replace inner LazyVStack with VStack LazyVStack { ForEach(...) { section in VStack { // ← Changed from LazyVStack ForEach(...) { row in ... } } } } Workaround 2: Embed in TabView TabView { NavigationStack { NestedLazyVStackView() // ← Same nested structure, but no hang } .tabItem { ... } } Interestingly, wrapping the entire navigation stack in a TabView prevents the hang entirely, even with the nested LazyVStack structure intact. Questions for Apple Is there a known issue with nested LazyVStack containers and accessibility traversal? Why does wrapping the view in a TabView prevent the hang? Are there recommended patterns for using nested lazy containers with accessibility support? Is this a timing issue, a deadlock, or an infinite loop in the accessibility system? Why that happens? Reproduction Project A complete, minimal reproduction project is available at: https://github.com/pendo-io/SwiftUI_Hang_Reproduction

How can I enable an external display in the Device Hub via Xcode 27, similar to the external display option previously available in the Simulator?

Hello, I have been unable to install any development-signed app on any physical device for five months. Builds succeed, code signing passes locally, but every device rejects the app at install time with: Failed to verify code signature of .../extracted/MyApp.app : 0xe8008018 (The identity used to sign the executable is no longer valid.) ApplicationVerificationFailed The app installs briefly, then iOS immediately removes it. This started right after my account (Team ID MB4DXDTDMT) was reinstated following a duplicate-account flag. Background: I had a personal account that was converted to a business account (Wakeout LLC), then created a new personal account, which Apple flagged as a duplicate and later reinstated. The signing failure began immediately after that reinstatement. Isolation already done (this is not a local-setup problem) I have run the full isolation sequence — including every step DTS typically asks for — and the result points squarely at the account/team, not my machine: New blank Xcode project, automatic signing, new bundle ID → same 0xe8008018. Brand-new macOS user account → same failure. Multiple Macs, fresh Xcode installs → same failure. Multiple iOS devices (iPhone 17 Pro, iPhone 15 Pro, others) → same failure. Different Apple ID / different developer team on the same Mac + same device → installs fine. This is the decisive one: the local environment is healthy; only Team MB4DXDTDMT is rejected. Xcode Cloud builds for this same team install fine. Apple's cloud signing trusts MB4DXDTDMT; the device-verification backend does not. That gap can only exist server-side. I have also: revoked/regenerated all certificates multiple times, deleted/recreated all provisioning profiles, cleared ~/Library/MobileDevice/Provisioning Profiles, cleared DerivedData and CoreDevice, removed device pairing records, re-paired devices, confirmed Developer Mode and correct system time. Simulators work. codesign --verify --deep --strict passes. Profile certificate SHA-1 matches the signing cert exactly. Entitlements match. Why I'm posting here This is the same failure documented in thread 755762, where Quinn concluded: "this seems to be tied to your primary developer account and only DevPrograms has access to those details." That matches my evidence exactly: the problem isolates cleanly to one team, and only DevPrograms can see the account-side state. I've already gone through Developer Support on this — an open case has been with them for about five months without a resolution, which is what convinced me the fix isn't something I can reach from the support side. I'm posting here in case a DTS engineer can confirm the diagnosis and point me to the right path. Question for any DTS engineer: given that the failure isolates to a single team — different teams sign and install fine on the same Mac and same device, and Xcode Cloud builds for this same team install fine — can you confirm this is an account-side signing-trust state that has to be reset by Apple, and what's the most direct way to get that reset actioned? Happy to attach a sysdiagnose, full console output, or codesign -dvvv dumps on request. Thank you.

Is there a known workaround (other than forking) for watchOS builds in Xcode 27 that depend on packages without a declared watchOS 9.0 floor? I depend on several Apple SPM packages with no minimum deployment target, such as https://github.com/apple/swift-algorithms. My project's minimum is 26.0. Xcode 27 will not build watchOS targets with these packages because watchOS 8.0 is below its range of supported targets. /.../SourcePackages/checkouts/swift-algorithms/Package.swift The watchOS Simulator deployment target 'WATCHOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 27.0.x.