Build, test, and submit your app using Xcode, Apple's integrated development environment.

Xcode Documentation

Posts under Xcode subtopic

Post

Replies

Boosts

Views

Activity

Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This suggests Xcode may be waiting on a Source Control authentication or host fingerprint UI flow that never resolves. SSH connectivity itself is functioning correctly: ssh -T git@bitbucket.org and ssh -T git@github.com both authenticate successfully. git ls-remote, git fetch, git pull, and git push all work correctly from Terminal. No Source Control accounts are configured in Xcode Preferences. Authentication relies entirely on SSH keys. Steps to Reproduce Configure an SSH key for Git access (e.g., Bitbucket or GitHub) and confirm it works via Terminal. Clone or open an existing Git repository that uses SSH (git@host:repo.git). Open the project/workspace in Xcode. In Xcode, attempt a Source Control operation such as: Source Control → Pull Source Control → Push Observe that Xcode displays a spinning progress indicator and does not complete the operation. Logs available on this Feedback Assist ID: FB22146913
10
11
1.1k
2w
Generate Preview Artifact in Xcode 27 Agentic AI
Been working for several days trying to figure out a solution. I'm building a plugin to bring in OpenRouter into Xcode so you can choose pretty much whatever cloud LLM you want easily. One thing I'm having trouble with is artifacts in the right hand pane. Specifically in /plan mode. Currently, it will write the plan in the transcript, it will even create a markdown card, but it will not put it in the artifact pane for preview and inline comment annotation for the next prompt. I can't seem to find the answer. Any help would be appreciated.
2
0
561
2w
Xcode 26.5 can't run apps on visionOS 27 and iOS 27 Beta 2
With Xcode Version 26.5 (17F42) apps can no longer be launched on a real Vision Pro once migrated to visionOS 27 Beta 2. At launch there is an EXC_BAD_ACCESS runtime error in an initialiser. If you launch apps on a real iPhone/Ipad with OS 27 Beta 2 the program will stop before the end of its start, but there is no precise line with the error. Xcode just stop in assembly code in the debugger, in the init phase of Swift where it searches for which objects to instantiate at launch. After investigating, the error comes from a debug setting from Xcode to show the stack trace. To avoid the error when run from Xcode Version 26.5 (17F42) In Xcode, open Product > Scheme > Edit Scheme. Select the Run action in the sidebar, then open the Options tab. Find Queue Debugging and uncheck Enable backtrace recording. If Queue debugging is enabled, then the program crashes when launched It is useful to be able to run apps from the production Xcode to devices with 27 OSes in beta to be able to test that everything will work fine for new versions of apps released before OSes 27 release. Thank you A previous post was made but the cause was badly identified. New Feedback including a sample code FB23384318
7
0
697
2w
Parallel swift testing on multiple ios simulators
Due to massive amount of shared state in my project I cannot really use swift testing parallelization in my tests, so my idea was to embed all suites into single one with .serialized and then run them on several simulators to speed up the tests. I ran tests with xcodebuild ... -parallel-testing-enabled YES -parallel-testing-worker-count 2, but swift testing suites seemed to be executed on just one simulator. Is it possible to run swift testing tests in parallel on multiple iOS simulators, but serially within each of them? Or the only way is xctest?
1
0
285
2w
Xcode 26.6 no longer shows the built-in Agents (Codex / Claude Agent) in Intelligence settings
After upgrading from Xcode 26.5 to Xcode 26.6, I noticed that the built-in Agents section has changed. My environment Xcode 26.6 (Build 17F113) macOS 26.5.2 (Build 25F84) Installed from the Mac App Store Signed in with my Apple ID in Xcode Apple Intelligence is enabled Chat providers work normally (ChatGPT, Claude, Google) What I expected According to Apple's documentation, the Intelligence settings should display built-in Agents such as: Claude Agent Codex with a Get button to install them. Reference: https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence What actually happens After upgrading to Xcode 26.6, the Agents section only contains: Allow external agents to use Xcode tools Add an Agent... The built-in Agents (Claude Agent and Codex) are completely missing. The Chat section still works normally. Comparison On the same Mac: Xcode 26.5 shows: Claude Agent Codex Get buttons Xcode 26.6 only shows MCP ("Allow external agents to use Xcode tools") and "Add an Agent...", with no built-in Agents. Things I have already tried Deleted all Xcode preferences Deleted ~/Library/Developer Deleted ~/Library/Application Support/Xcode Reinstalled Xcode 26.6 Signed out/in of Apple ID Verified Intelligence is enabled No change. Additional information The following directory is never created: ~/Library/Developer/Xcode/CodingAssistant Searching Xcode preferences also shows no Agent-related configuration. Question Is this an intentional change in Xcode 26.6, or is this a bug? If it's expected, how can I restore the built-in Agent catalog (Claude Agent / Codex)? Thanks!
5
4
456
2w
Xcode 26.6 no longer shows the built-in Agents (Codex / Claude Agent) in Intelligence settings
Installed from the Mac App Store Signed in with my Apple ID in Xcode Apple Intelligence is enabled Chat providers work normally (ChatGPT, Claude, Google) What I expected According to Apple's documentation, the Intelligence settings should display built-in Agents such as: Claude Agent Codex with a Get button to install them. Reference: https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence What actually happens After upgrading to Xcode 26.6, the Agents section only contains: Allow external agents to use Xcode tools Add an Agent... The built-in Agents (Claude Agent and Codex) are completely missing.
1
2
298
2w
Choosing "Default" model in Claude Coding Intelligence Setting in Xcode but overriden by ANTHROPIC_MODEL=best env var and Fable got used & cause 5hr Max 5X token quota reached 100% from 0% in 2 min 😢😢😭
Never have this problem running in the first version of Xcode 27 until download the latest Xcode 27. At least "Fable" should be added in the dropdown to give a sense that it could be selected and be more careful (in dropdown only have "Sonnet", "Opus", "Sonnet+Opus" and more) I also submit Feedback request FB23973503 with screen capture & more Xcode Claude AI Investigation details
1
0
377
2w
Command Line Tools bundled Python 3.9.6 flagged by vulnerability scanner
We need guidance regarding the Python runtime bundled with Apple Command Line Tools. Environment: macOS Tahoe 26.5.2 (25F84) Xcode 26.6 (17F113) Device type: Mac Command Line Tools Python path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/ Version confirmed locally with: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/bin/python3 --version Output: Python 3.9.6 Our vulnerability-management platform, Qualys, reports this Apple Command Line Tools Python runtime as vulnerable under QID 387170, referencing CVE-2022-4303 and CVE-2023-0286. The detection points to: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/Resources/Python.app My understanding is that this runtime is bundled and managed by Apple as part of Command Line Tools, and that manually replacing or modifying this framework is not a supported remediation path. Installing a separate standalone Python version also does not remediate the finding at this Apple-managed path. Could Apple or the community confirm the supported approach for this scenario? Specifically: Is Python 3.9.6 intentionally bundled with the current Command Line Tools release for this macOS/Xcode version? Has Apple applied security fixes or backports to this bundled Python runtime that are not reflected in the upstream Python version number? Is updating Command Line Tools/Xcode the only supported remediation method for this component? Is manually replacing or modifying the bundled Python framework unsupported? Is there any known mitigation or official guidance for vulnerability-management exceptions while waiting for an Apple-provided update? I have also filed this through Feedback Assistant: FB23893693. Any official Apple guidance or reference to existing documentation would be very helpful, as we need to provide an auditable response to our internal security and audit teams.
7
0
666
2w
Xcode 26.6 (17F113) -Onone: UIScene.ActivationState enum comparison crashes at runtime (works in Release)
Summary On Xcode 26.6 (17F113) / Swift 6.2, a Debug build (-Onone) crashes at runtime when comparing UIScene.ActivationState inside a closure passed to Array.first(where:). The exact same code runs fine when built with optimizations (-O / Release). This looks like an -Onone code-generation (miscompile) bug rather than a logic error in the app. Environment Xcode: 26.6 (17F113) Toolchain: Swift 6.2 (Apple default toolchain) Optimization: SWIFT_OPTIMIZATION_LEVEL = -Onone (Debug scheme) Deployment target: [ iOS xx.x ] Run destination: [ Device / Simulator — model, OS version ] Configuration: also reproduces in a fresh checkout after Clean Build Folder + DerivedData wipe Steps to Reproduce Add the following to any app and call it early in the launch path (e.g. from an async context / Task during startup): import UIKit enum ScreenUtil { static var keyScene: UIWindowScene? { let scenes = UIApplication.shared.connectedScenes .compactMap { $0 as? UIWindowScene } // Crashes here in Debug (-Onone) on Xcode 26.6 (17F113) return scenes.first { $0.activationState == .foregroundActive } ?? scenes.first } } 2. Build and run with the Debug scheme (-Onone). 3. The app crashes as soon as keyScene is evaluated. Expected keyScene returns the foreground-active UIWindowScene (or the first scene), identically to the optimized build. Actual Immediate crash when the closure evaluates $0.activationState == .foregroundActive. UIScene.ActivationState is an Objective-C-imported (NSInteger-backed) enum, and the failure appears tied to how its value is handled under -Onone. The crash surfaces inside Swift concurrency resume plumbing because keyScene is reached from an async context at launch. Representative frame: (1) await resume partial function for partial apply forwarder for reabstraction thunk helper ... @isolated(any) @callee_guaranteed @async () -> (@out τ_0_0) ... -> ldr x0, [x22, #0x8] ; faults here br x0 ; preceding: bl swift_task_dealloc Reproducibility - Debug (-Onone): crashes 100% - Release (-O): works correctly Workaround Rewriting the closure comparison as an explicit loop avoids the crash: static var keyScene: UIWindowScene? { let scenes = UIApplication.shared.connectedScenes .compactMap { $0 as? UIWindowScene } for scene in scenes where scene.activationState == .foregroundActive { return scene } return scenes.first } Notes A sysdiagnose / crash log and a minimal sample project are attached via Feedback Assistant (FB[ number ]). Happy to provide additional details.
0
0
319
2w
Device Hub sucks
Or maybe I suck? Is there really no way with the new Xcode to take a simple screenshot from the device you're testing?You have to connect this Device Hub? An entirely separate app. And not only that, then you have to pair it, which maintains a live connection to the phone? Fine. Okay then. But now I can no longer test the microphone functions of my app because that shared session is interfering with it. Oh, well, I'll just disconnect the session then, right? Nope. The button to disconnect the session doesn't work. Device Hub thinks it's disconnected, but my phone still shows the blue sharing session icon in the upper left hand corner. The only way to stop that is to unpair the phone completely. So then every time I want to take a screenshot, I've got to do this pairing crap? I think I'll be running a second copy of Xcode 26 for quite a while just to use the screenshot button.
5
0
315
2w
Apple watch series 9 (OS 10.3) not showing up in xcode 15.1 under devices list.
When connecting my iphone (14pro with iOS 17.2.1) with a paired apple watch (series 9 with OS 10.3), it is not showing up on the devices/simulators list in xcode 15.1. Beyond unpairing/repairing the watch, restarting either iphone or watch, connecting/disconnecting the iphone from the computer or deleting xcode and re-installing xcode, any other suggestions? Under the WatchApp field it shows "no eligible device connected", however, under the console the Apple Watch does appear. I have tried just about everything and can't get the watch to appear in Xcode. I am running all this on a MacBook Pro with Sonoma. Thanks for any assistance!
1
1
1.3k
2w
Xcode won't sign into ChatGPT Codex account anymore
As of May 8th, 2026, after I upgraded to "codex-cli 0.129.0" via Xcode, I can no longer sign into my ChatGPT account in Xcode Intelligence Settings. The Log In window is always successful, but the settings never update to show the login being successful. It's a constant loop. Perhaps a hand-shake fail. Versions: Tahoe 26.3.1, Xcode 26.4.1, codex-cli 0.129.0.
12
4
1.8k
2w
Xcode Codex sign-in fails after updating OpenAI component
Environment: macOS: Tahoe 26.4 Xcode: 26.5 ChatGPT account successfully authenticated Codex CLI installed and working Codex App installed and working Steps to reproduce: Install Xcode Codex/OpenAI component version where GPT-5.4 is the highest available model. Sign in with ChatGPT account. Confirm Codex works in Xcode. Update the OpenAI/Codex component in Xcode. Attempt to sign in again. Expected result: Xcode completes authentication and shows signed-in status. Actual result: Browser successfully completes authentication and displays "Signed in to Codex." Xcode remains in a sign-in loop or shows "Not Signed In." Authentication never completes. Additional observations: Codex CLI authentication succeeds. Codex App authentication succeeds. ChatGPT web/app access succeeds. Anthropic/Claude component updates continue to work normally in Xcode. Issue appears specific to the updated OpenAI/Codex Xcode component. Older component (GPT-5.4 maximum model available) authenticates successfully.
5
5
788
2w
Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This suggests Xcode may be waiting on a Source Control authentication or host fingerprint UI flow that never resolves. SSH connectivity itself is functioning correctly: ssh -T git@bitbucket.org and ssh -T git@github.com both authenticate successfully. git ls-remote, git fetch, git pull, and git push all work correctly from Terminal. No Source Control accounts are configured in Xcode Preferences. Authentication relies entirely on SSH keys. Steps to Reproduce Configure an SSH key for Git access (e.g., Bitbucket or GitHub) and confirm it works via Terminal. Clone or open an existing Git repository that uses SSH (git@host:repo.git). Open the project/workspace in Xcode. In Xcode, attempt a Source Control operation such as: Source Control → Pull Source Control → Push Observe that Xcode displays a spinning progress indicator and does not complete the operation. Logs available on this Feedback Assist ID: FB22146913
Replies
10
Boosts
11
Views
1.1k
Activity
2w
Generate Preview Artifact in Xcode 27 Agentic AI
Been working for several days trying to figure out a solution. I'm building a plugin to bring in OpenRouter into Xcode so you can choose pretty much whatever cloud LLM you want easily. One thing I'm having trouble with is artifacts in the right hand pane. Specifically in /plan mode. Currently, it will write the plan in the transcript, it will even create a markdown card, but it will not put it in the artifact pane for preview and inline comment annotation for the next prompt. I can't seem to find the answer. Any help would be appreciated.
Replies
2
Boosts
0
Views
561
Activity
2w
How to create a local package in Xcode 27?
Xcode 27 beta 4: how do I create a local package for my project? The menu path File > New > Package no longer exists.
Replies
1
Boosts
0
Views
298
Activity
2w
Xcode 26.5 can't run apps on visionOS 27 and iOS 27 Beta 2
With Xcode Version 26.5 (17F42) apps can no longer be launched on a real Vision Pro once migrated to visionOS 27 Beta 2. At launch there is an EXC_BAD_ACCESS runtime error in an initialiser. If you launch apps on a real iPhone/Ipad with OS 27 Beta 2 the program will stop before the end of its start, but there is no precise line with the error. Xcode just stop in assembly code in the debugger, in the init phase of Swift where it searches for which objects to instantiate at launch. After investigating, the error comes from a debug setting from Xcode to show the stack trace. To avoid the error when run from Xcode Version 26.5 (17F42) In Xcode, open Product > Scheme > Edit Scheme. Select the Run action in the sidebar, then open the Options tab. Find Queue Debugging and uncheck Enable backtrace recording. If Queue debugging is enabled, then the program crashes when launched It is useful to be able to run apps from the production Xcode to devices with 27 OSes in beta to be able to test that everything will work fine for new versions of apps released before OSes 27 release. Thank you A previous post was made but the cause was badly identified. New Feedback including a sample code FB23384318
Replies
7
Boosts
0
Views
697
Activity
2w
Parallel swift testing on multiple ios simulators
Due to massive amount of shared state in my project I cannot really use swift testing parallelization in my tests, so my idea was to embed all suites into single one with .serialized and then run them on several simulators to speed up the tests. I ran tests with xcodebuild ... -parallel-testing-enabled YES -parallel-testing-worker-count 2, but swift testing suites seemed to be executed on just one simulator. Is it possible to run swift testing tests in parallel on multiple iOS simulators, but serially within each of them? Or the only way is xctest?
Replies
1
Boosts
0
Views
285
Activity
2w
Xcode 27 beta - Device Hub - Missing "Slow animations"
Where did the simulator "Slow animations" mode go? I can't find it in the Xcode 27 beta 2 "Device Hub". This feature is incredibly useful. I'm assuming it's a glitch that it's missing, or I'm just not looking in the right place.
Replies
3
Boosts
4
Views
413
Activity
2w
Xcode 26.6 no longer shows the built-in Agents (Codex / Claude Agent) in Intelligence settings
After upgrading from Xcode 26.5 to Xcode 26.6, I noticed that the built-in Agents section has changed. My environment Xcode 26.6 (Build 17F113) macOS 26.5.2 (Build 25F84) Installed from the Mac App Store Signed in with my Apple ID in Xcode Apple Intelligence is enabled Chat providers work normally (ChatGPT, Claude, Google) What I expected According to Apple's documentation, the Intelligence settings should display built-in Agents such as: Claude Agent Codex with a Get button to install them. Reference: https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence What actually happens After upgrading to Xcode 26.6, the Agents section only contains: Allow external agents to use Xcode tools Add an Agent... The built-in Agents (Claude Agent and Codex) are completely missing. The Chat section still works normally. Comparison On the same Mac: Xcode 26.5 shows: Claude Agent Codex Get buttons Xcode 26.6 only shows MCP ("Allow external agents to use Xcode tools") and "Add an Agent...", with no built-in Agents. Things I have already tried Deleted all Xcode preferences Deleted ~/Library/Developer Deleted ~/Library/Application Support/Xcode Reinstalled Xcode 26.6 Signed out/in of Apple ID Verified Intelligence is enabled No change. Additional information The following directory is never created: ~/Library/Developer/Xcode/CodingAssistant Searching Xcode preferences also shows no Agent-related configuration. Question Is this an intentional change in Xcode 26.6, or is this a bug? If it's expected, how can I restore the built-in Agent catalog (Claude Agent / Codex)? Thanks!
Replies
5
Boosts
4
Views
456
Activity
2w
Xcode 26.6 no longer shows the built-in Agents (Codex / Claude Agent) in Intelligence settings
Installed from the Mac App Store Signed in with my Apple ID in Xcode Apple Intelligence is enabled Chat providers work normally (ChatGPT, Claude, Google) What I expected According to Apple's documentation, the Intelligence settings should display built-in Agents such as: Claude Agent Codex with a Get button to install them. Reference: https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence What actually happens After upgrading to Xcode 26.6, the Agents section only contains: Allow external agents to use Xcode tools Add an Agent... The built-in Agents (Claude Agent and Codex) are completely missing.
Replies
1
Boosts
2
Views
298
Activity
2w
Choosing "Default" model in Claude Coding Intelligence Setting in Xcode but overriden by ANTHROPIC_MODEL=best env var and Fable got used & cause 5hr Max 5X token quota reached 100% from 0% in 2 min 😢😢😭
Never have this problem running in the first version of Xcode 27 until download the latest Xcode 27. At least "Fable" should be added in the dropdown to give a sense that it could be selected and be more careful (in dropdown only have "Sonnet", "Opus", "Sonnet+Opus" and more) I also submit Feedback request FB23973503 with screen capture & more Xcode Claude AI Investigation details
Replies
1
Boosts
0
Views
377
Activity
2w
Codex integration just stopped working
Nothing changed on my end, Pro subscription still active, but Xcode 26.5 (17F42) simply does not want to log into Codex anymore. It opens the OAuth flow and after finishing and closing the window, it still says "Not Signed In". Codex login works everywhere else, including the Codex app. What to do?
Replies
29
Boosts
4
Views
2.3k
Activity
2w
Command Line Tools bundled Python 3.9.6 flagged by vulnerability scanner
We need guidance regarding the Python runtime bundled with Apple Command Line Tools. Environment: macOS Tahoe 26.5.2 (25F84) Xcode 26.6 (17F113) Device type: Mac Command Line Tools Python path: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/ Version confirmed locally with: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/bin/python3 --version Output: Python 3.9.6 Our vulnerability-management platform, Qualys, reports this Apple Command Line Tools Python runtime as vulnerable under QID 387170, referencing CVE-2022-4303 and CVE-2023-0286. The detection points to: /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/Resources/Python.app My understanding is that this runtime is bundled and managed by Apple as part of Command Line Tools, and that manually replacing or modifying this framework is not a supported remediation path. Installing a separate standalone Python version also does not remediate the finding at this Apple-managed path. Could Apple or the community confirm the supported approach for this scenario? Specifically: Is Python 3.9.6 intentionally bundled with the current Command Line Tools release for this macOS/Xcode version? Has Apple applied security fixes or backports to this bundled Python runtime that are not reflected in the upstream Python version number? Is updating Command Line Tools/Xcode the only supported remediation method for this component? Is manually replacing or modifying the bundled Python framework unsupported? Is there any known mitigation or official guidance for vulnerability-management exceptions while waiting for an Apple-provided update? I have also filed this through Feedback Assistant: FB23893693. Any official Apple guidance or reference to existing documentation would be very helpful, as we need to provide an auditable response to our internal security and audit teams.
Replies
7
Boosts
0
Views
666
Activity
2w
Xcode 26.6 (17F113) -Onone: UIScene.ActivationState enum comparison crashes at runtime (works in Release)
Summary On Xcode 26.6 (17F113) / Swift 6.2, a Debug build (-Onone) crashes at runtime when comparing UIScene.ActivationState inside a closure passed to Array.first(where:). The exact same code runs fine when built with optimizations (-O / Release). This looks like an -Onone code-generation (miscompile) bug rather than a logic error in the app. Environment Xcode: 26.6 (17F113) Toolchain: Swift 6.2 (Apple default toolchain) Optimization: SWIFT_OPTIMIZATION_LEVEL = -Onone (Debug scheme) Deployment target: [ iOS xx.x ] Run destination: [ Device / Simulator — model, OS version ] Configuration: also reproduces in a fresh checkout after Clean Build Folder + DerivedData wipe Steps to Reproduce Add the following to any app and call it early in the launch path (e.g. from an async context / Task during startup): import UIKit enum ScreenUtil { static var keyScene: UIWindowScene? { let scenes = UIApplication.shared.connectedScenes .compactMap { $0 as? UIWindowScene } // Crashes here in Debug (-Onone) on Xcode 26.6 (17F113) return scenes.first { $0.activationState == .foregroundActive } ?? scenes.first } } 2. Build and run with the Debug scheme (-Onone). 3. The app crashes as soon as keyScene is evaluated. Expected keyScene returns the foreground-active UIWindowScene (or the first scene), identically to the optimized build. Actual Immediate crash when the closure evaluates $0.activationState == .foregroundActive. UIScene.ActivationState is an Objective-C-imported (NSInteger-backed) enum, and the failure appears tied to how its value is handled under -Onone. The crash surfaces inside Swift concurrency resume plumbing because keyScene is reached from an async context at launch. Representative frame: (1) await resume partial function for partial apply forwarder for reabstraction thunk helper ... @isolated(any) @callee_guaranteed @async () -> (@out τ_0_0) ... -> ldr x0, [x22, #0x8] ; faults here br x0 ; preceding: bl swift_task_dealloc Reproducibility - Debug (-Onone): crashes 100% - Release (-O): works correctly Workaround Rewriting the closure comparison as an explicit loop avoids the crash: static var keyScene: UIWindowScene? { let scenes = UIApplication.shared.connectedScenes .compactMap { $0 as? UIWindowScene } for scene in scenes where scene.activationState == .foregroundActive { return scene } return scenes.first } Notes A sysdiagnose / crash log and a minimal sample project are attached via Feedback Assistant (FB[ number ]). Happy to provide additional details.
Replies
0
Boosts
0
Views
319
Activity
2w
Mac alert: "Allow ServiceExtensio to find devices on local networks?"
I'm on a Mac. I have Xcode installed but it's not running, nor is the Simulator. And yet Mac pops up an alert asking, ""Allow ServiceExtensio to find devices on local networks?" Creepy! No you can't scan my network. What gives? And why not tell me your real name?
Replies
0
Boosts
0
Views
80
Activity
2w
Regression in Unicode handling in Xcode 27 text editor
Emoji handling (usually a sign of underlying Unicode bugs) is broken in Xcode 27, all betas: The issue doesn't exist in previous Xcode source editors. FB23969935
Replies
4
Boosts
0
Views
626
Activity
2w
Can't use /uikit-app-modernization
When will this be available? (Opencode + LMStudio + Qwen 3.6 27B) FB23978071
Replies
0
Boosts
0
Views
102
Activity
2w
Device Hub sucks
Or maybe I suck? Is there really no way with the new Xcode to take a simple screenshot from the device you're testing?You have to connect this Device Hub? An entirely separate app. And not only that, then you have to pair it, which maintains a live connection to the phone? Fine. Okay then. But now I can no longer test the microphone functions of my app because that shared session is interfering with it. Oh, well, I'll just disconnect the session then, right? Nope. The button to disconnect the session doesn't work. Device Hub thinks it's disconnected, but my phone still shows the blue sharing session icon in the upper left hand corner. The only way to stop that is to unpair the phone completely. So then every time I want to take a screenshot, I've got to do this pairing crap? I think I'll be running a second copy of Xcode 26 for quite a while just to use the screenshot button.
Replies
5
Boosts
0
Views
315
Activity
2w
Xcode IOS development
Super noob here 😅 is there a way to work with the “Xcode” development app on IOS. Any advice or input is welcome.
Replies
1
Boosts
0
Views
287
Activity
2w
Apple watch series 9 (OS 10.3) not showing up in xcode 15.1 under devices list.
When connecting my iphone (14pro with iOS 17.2.1) with a paired apple watch (series 9 with OS 10.3), it is not showing up on the devices/simulators list in xcode 15.1. Beyond unpairing/repairing the watch, restarting either iphone or watch, connecting/disconnecting the iphone from the computer or deleting xcode and re-installing xcode, any other suggestions? Under the WatchApp field it shows "no eligible device connected", however, under the console the Apple Watch does appear. I have tried just about everything and can't get the watch to appear in Xcode. I am running all this on a MacBook Pro with Sonoma. Thanks for any assistance!
Replies
1
Boosts
1
Views
1.3k
Activity
2w
Xcode won't sign into ChatGPT Codex account anymore
As of May 8th, 2026, after I upgraded to "codex-cli 0.129.0" via Xcode, I can no longer sign into my ChatGPT account in Xcode Intelligence Settings. The Log In window is always successful, but the settings never update to show the login being successful. It's a constant loop. Perhaps a hand-shake fail. Versions: Tahoe 26.3.1, Xcode 26.4.1, codex-cli 0.129.0.
Replies
12
Boosts
4
Views
1.8k
Activity
2w
Xcode Codex sign-in fails after updating OpenAI component
Environment: macOS: Tahoe 26.4 Xcode: 26.5 ChatGPT account successfully authenticated Codex CLI installed and working Codex App installed and working Steps to reproduce: Install Xcode Codex/OpenAI component version where GPT-5.4 is the highest available model. Sign in with ChatGPT account. Confirm Codex works in Xcode. Update the OpenAI/Codex component in Xcode. Attempt to sign in again. Expected result: Xcode completes authentication and shows signed-in status. Actual result: Browser successfully completes authentication and displays "Signed in to Codex." Xcode remains in a sign-in loop or shows "Not Signed In." Authentication never completes. Additional observations: Codex CLI authentication succeeds. Codex App authentication succeeds. ChatGPT web/app access succeeds. Anthropic/Claude component updates continue to work normally in Xcode. Issue appears specific to the updated OpenAI/Codex Xcode component. Older component (GPT-5.4 maximum model available) authenticates successfully.
Replies
5
Boosts
5
Views
788
Activity
2w