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 27 beta 2 almost impossible to use with 16 GB memory Macs.
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.
3
2
134
2d
Xcode 27 Beta / Beta 2 Running my app in Device Hub stalls on Launch Screen
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.
1
0
104
2d
ChatGPT stopped working in Xcode
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
1
0
62
2d
Xcode 27 incorrectly links a Catalyst binary, _UIFontTextStyleCallout Expected in AppKit
I have a personal iOS project that I also compile for macOS with Catalyst. When built with Xcode 26.x, everything is linked correctly. When built with Xcode 27 betas, the following runtime error occurs: Termination Reason: Namespace DYLD, Code 4, Symbol missing Symbol not found: _UIFontTextStyleCallout Referenced from: <046ED276-F81A-31B4-82FF-6DC82E9041BC> /Applications/Photo Library.app/Contents/MacOS/Photo Library Expected in: <298B64F6-9BC0-3BFB-BE72-EBDC2BE0FF19> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit Any assistance? Thanks
2
0
94
3d
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.
8
2
1.2k
3d
Xcode on my new MacBook will not find my iPhone
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?
0
0
38
3d
Interface Builder is barely usable
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.
4
0
184
3d
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
3
0
152
3d
opencode + LM studio + plan = sad
quencoder 2.5 locally is making great plans. Beautiful plans amazing plans that are so correct I want to hug it. But when I want to implement it there is no button asking me if I want to go ahead. I tried /exit-plan and the command could not be completed (I only see /plan, /rename, and /exit-planP. I do not see the markdown in a separate pane that's copyable as shown in this video https://developer.apple.com/videos/play/wwdc2026/259/?time=597 (I also can't get the conversation in a separate window by pressing option shift click, I have to manually open the conversation in a new tab). I get a plan interleaved with code snippets and I can't copy the whole plan to a new conversation. I would very much like this to work. (I also really like being able to run locally because I do not agree with google, openai, or anthropic ethics. thanks for giving me a choice) (I also like how not like a sycophant the tone of the response is. refreshing) (Note I started planning first because without a plan it started mucking about in the plist editing status bar keys when the problem was a navigation bar which I thought was clear from the picture I attached) (But I'd really like to say go and I have no buttons to exit plan mode.) (I am going to stay on Tahoe till October) I asked it how to copy and it said: In the opencode session where the plan was discussed, type /share — it'll copy a shareable link to your clipboard (like opncd.ai/s/...). Paste that link here and I can fetch the plan directly. That was a hallucination when I typed /share the agent just repeated its plan for a third time. It's a good plan, the best plan, I don't see any algae in this plan. It also said "I can see from the repository exploration that there's no written plan document, and the other agent is working on "[the plan]." However, I don't have access to the previous conversation's last response. Maybe there should be a button to copy a whole response or open a new conversation (not in plan mode) with a response? I see that I can configure agents https://opencode.ai/docs/agents/. Should I? Shouldn't Xcode do it for me? { "$schema": "https://opencode.ai/config.json", "agent": { "build": { "mode": "primary", "model": "anthropic/claude-sonnet-4-20250514", "prompt": "{file:./prompts/build.txt}", "permission": { "edit": "allow", "bash": "allow" } }, "plan": { "mode": "primary", "model": "anthropic/claude-haiku-4-20250514", "permission": { "edit": "deny", "bash": "deny" } }, "code-reviewer": { "description": "Reviews code for best practices and potential issues", "mode": "subagent", "model": "anthropic/claude-sonnet-4-20250514", "prompt": "You are a code reviewer. Focus on security, performance, and maintainability.", "permission": { "edit": "deny" } } } }
5
0
138
4d
Xcode 26.4: IBOutlets/IBActions gutter circles missing — cannot connect storyboard to code (works in 26.3)
I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.
31
12
3.4k
4d
Default widget extension not configurable on Mac
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.
0
0
42
4d
Xcode 27 Agent is impossible to work with.
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
6
2
343
5d
Metal Toolchain not matching xCode Beta 27
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.
1
0
79
5d
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/docum
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.
0
0
30
5d
Differences between cloud and local models in Xcode Intelligence
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.
3
0
220
5d
Application Hangs with Nested LazyVStack When Accessibility Inspector is Active
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
8
0
616
5d
Xcode 27 beta 2 almost impossible to use with 16 GB memory Macs.
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.
Replies
3
Boosts
2
Views
134
Activity
2d
Xcode 27 Beta / Beta 2 Running my app in Device Hub stalls on Launch Screen
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.
Replies
1
Boosts
0
Views
104
Activity
2d
ChatGPT stopped working in Xcode
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
Replies
1
Boosts
0
Views
62
Activity
2d
Xcode 27 incorrectly links a Catalyst binary, _UIFontTextStyleCallout Expected in AppKit
I have a personal iOS project that I also compile for macOS with Catalyst. When built with Xcode 26.x, everything is linked correctly. When built with Xcode 27 betas, the following runtime error occurs: Termination Reason: Namespace DYLD, Code 4, Symbol missing Symbol not found: _UIFontTextStyleCallout Referenced from: <046ED276-F81A-31B4-82FF-6DC82E9041BC> /Applications/Photo Library.app/Contents/MacOS/Photo Library Expected in: <298B64F6-9BC0-3BFB-BE72-EBDC2BE0FF19> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit Any assistance? Thanks
Replies
2
Boosts
0
Views
94
Activity
3d
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
8
Boosts
2
Views
1.2k
Activity
3d
Xcode on my new MacBook will not find my iPhone
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?
Replies
0
Boosts
0
Views
38
Activity
3d
Interface Builder is barely usable
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.
Replies
4
Boosts
0
Views
184
Activity
3d
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
3
Boosts
0
Views
152
Activity
3d
The iOS project runs via Xcode, but the watch app cannot be installed on the watch, showing the message "This app could not be installed at this time. Could not install at this time." However, the build distributed through TestFlight installs normall
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?
Replies
2
Boosts
0
Views
134
Activity
3d
opencode + LM studio + plan = sad
quencoder 2.5 locally is making great plans. Beautiful plans amazing plans that are so correct I want to hug it. But when I want to implement it there is no button asking me if I want to go ahead. I tried /exit-plan and the command could not be completed (I only see /plan, /rename, and /exit-planP. I do not see the markdown in a separate pane that's copyable as shown in this video https://developer.apple.com/videos/play/wwdc2026/259/?time=597 (I also can't get the conversation in a separate window by pressing option shift click, I have to manually open the conversation in a new tab). I get a plan interleaved with code snippets and I can't copy the whole plan to a new conversation. I would very much like this to work. (I also really like being able to run locally because I do not agree with google, openai, or anthropic ethics. thanks for giving me a choice) (I also like how not like a sycophant the tone of the response is. refreshing) (Note I started planning first because without a plan it started mucking about in the plist editing status bar keys when the problem was a navigation bar which I thought was clear from the picture I attached) (But I'd really like to say go and I have no buttons to exit plan mode.) (I am going to stay on Tahoe till October) I asked it how to copy and it said: In the opencode session where the plan was discussed, type /share — it'll copy a shareable link to your clipboard (like opncd.ai/s/...). Paste that link here and I can fetch the plan directly. That was a hallucination when I typed /share the agent just repeated its plan for a third time. It's a good plan, the best plan, I don't see any algae in this plan. It also said "I can see from the repository exploration that there's no written plan document, and the other agent is working on "[the plan]." However, I don't have access to the previous conversation's last response. Maybe there should be a button to copy a whole response or open a new conversation (not in plan mode) with a response? I see that I can configure agents https://opencode.ai/docs/agents/. Should I? Shouldn't Xcode do it for me? { "$schema": "https://opencode.ai/config.json", "agent": { "build": { "mode": "primary", "model": "anthropic/claude-sonnet-4-20250514", "prompt": "{file:./prompts/build.txt}", "permission": { "edit": "allow", "bash": "allow" } }, "plan": { "mode": "primary", "model": "anthropic/claude-haiku-4-20250514", "permission": { "edit": "deny", "bash": "deny" } }, "code-reviewer": { "description": "Reviews code for best practices and potential issues", "mode": "subagent", "model": "anthropic/claude-sonnet-4-20250514", "prompt": "You are a code reviewer. Focus on security, performance, and maintainability.", "permission": { "edit": "deny" } } } }
Replies
5
Boosts
0
Views
138
Activity
4d
Xcode 26.4: IBOutlets/IBActions gutter circles missing — cannot connect storyboard to code (works in 26.3)
I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.
Replies
31
Boosts
12
Views
3.4k
Activity
4d
Xcode 27 beta deployment issue
Im unable to deploy Xcode 27 beta code to an iPhone 17 pro The build is successful but its not loading
Replies
1
Boosts
0
Views
95
Activity
4d
Select the model in Xcode
How do I select between GPT and Claude, and the model, when opening a new task for the coding agent with the ‘New Conversation’ button in the toolbar?
Replies
2
Boosts
1
Views
140
Activity
4d
Default widget extension not configurable on Mac
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.
Replies
0
Boosts
0
Views
42
Activity
4d
Xcode 27 Agent is impossible to work with.
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
Replies
6
Boosts
2
Views
343
Activity
5d
Settng up Grok as an Xcode Intelligence provider
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
Replies
3
Boosts
1
Views
512
Activity
5d
Metal Toolchain not matching xCode Beta 27
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.
Replies
1
Boosts
0
Views
79
Activity
5d
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/docum
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.
Replies
0
Boosts
0
Views
30
Activity
5d
Differences between cloud and local models in Xcode Intelligence
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.
Replies
3
Boosts
0
Views
220
Activity
5d
Application Hangs with Nested LazyVStack When Accessibility Inspector is Active
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
Replies
8
Boosts
0
Views
616
Activity
5d