I need to use Xcode version 16 for a college project. However, I cannot install it on my mac. M2Pro - ios Tahoe 26.2. Is there any workaround for this? Is my best option to downgrade to Sequoia? I'm a little apprehensive about this but willing to give it a try. Can anyone recommend a good, reliable video for this?

I work on some proprietary codebases and can only use private AI services with them (currently MiniMax M2.1 and GLM 4.7). It all works great with both Claude Code and OpenCode agents, and I'd like to leverage the new agentic capabilities that are now in Xcode 26.3. I'm not seeing any option to connect to OpenCode, and both the Anthropic and OpenAI providers require an enterprise account (which I don't have access to). Are there any options that I'm missing here?

My project is complete, I successfully compile the application, but when I try to run it on my simulator it gives an error, stating that the architecture is incorrect, even though it is parameterized for ARM architecture. Note: the application runs on my iPhone. Has anyone else had this problem?

Hello! I started to develop a Mac application in Xcode 15, under MacOS 13. I made several commits in this environment. Later, I switched to another Mac and continued the development in Xcode 26.2, under MacOS 26. Since then, I haven't been able to make commits. I staged the changes, inserted the message, but the commit button is inactive (non-clickable), as shown in the picture. Can anyone help me to get it to work again? Thank you in advance.

I have a Xcode project with two apps that have a separate MainMenu.nib file. Both are different apps with different source trees.. Why am I seeing resources in interface builder from one app in another? I am a bit old school and using the AppDelegate rather than view controllers to capture events... but that should work fine Thanks ahead of time.

Hey folks, Looking for some assistance with using an API key with xcodebuild commands to archive/export builds on our Enterprise developer account. The goal here is to allow Xcode to completely manage signing/certificates with our cloud distribution certificate, since these builds are happening in CI and we don't want to be manually handling user sessions/certificates on these machines. This is working great with our App Store account, but with our Enterprise account we're getting errors both archiving and exporting the builds. Here's an example of an export command that is giving errors: xcodebuild -exportArchive -exportOptionsPlist /path/to/exportOptions.plist -archivePath /path/to/archive.xcarchive -exportPath /path/to/export -authenticationKeyID *** -authenticationKeyIssuerID *** -authenticationKeyPath /path/to/key.p8 -allowProvisioningUpdates I've put some example values there, but we've double/triple checked the real values when this is actually running. These are the errors we're getting: 2026-02-02 12:30:04.022 xcodebuild[59722:1854348] DVTServices: Received response for 0794248F-E534-474D-ABBF-40C1375B6590 @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} 2026-02-02 12:30:04.173 xcodebuild[59722:1854348] DVTServices: Received response for 1D51FCD1-1876-4881-BE89-DD44E78EA776 @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} 2026-02-02 12:30:04.322 xcodebuild[59722:1854344] DVTServices: Received response for 25D7983F-1153-47C9-AE8A-03A8D10B6453 @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} 2026-02-02 12:30:04.483 xcodebuild[59722:1854344] DVTServices: Received response for 8A56C98B-E786-4878-856F-4D7E3D381DEA @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} error: exportArchive Communication with Apple failed error: exportArchive No signing certificate "iOS Distribution" found We get very similar errors when archiving as well. Are we doing something incorrect here? Is API key usage with xcodebuild not supported for Enterprise builds? Appreciate any help y'all can provide!

I’m attempting to install the Metal toolchain in Xcode, but the installation keeps hanging. Through Xcode, it stops at the “Processing” step, and via the terminal, it never goes past “Beginning asset download…”.

While debugging a Swift application in Xcode, LLDB crashes with an assertion failure related to LLDBMemoryReader and pointer authentication. The issue occurs during normal debugging (e.g. inspecting variables or stack frames), and causes the debugger to become unusable. The error appears to be triggered inside the Swift language runtime reflection path in LLDB error: Assertion failed: (LLDBMemoryReader module to address map ran into pointer authentication mask!), function addModuleToAddressMap, file /AppleInternal/Library/BuildRoots/603ae698-b099-11ef-b64c-aabfac210453/Library/Caches/com.apple.xbs/Sources/lldb/llvm-project/lldb/source/Plugins/LanguageRuntime/Swift/LLDBMemoryReader.cpp, line 537 Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it): 0 LLDB 0x00000001240eb8f8 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 40 1 LLDB 0x0000000123bbd0a8 lldb_private::lldb_assert(bool, char const*, char const*, char const*, unsigned int) + 184 2 LLDB 0x0000000123d5379d lldb_private::LLDBMemoryReader::addModuleToAddressMap(std::__1::shared_ptr<lldb_private::Module>, bool) + 477 3 LLDB 0x0000000123dbb733 lldb_private::SwiftLanguageRuntimeImpl::AddObjectFileToReflectionContext(std::__1::shared_ptr<lldb_private::Module>, llvm::SmallVector<llvm::StringRef, 1u>) + 1043 4 LLDB 0x0000000123dbc6de lldb_private::SwiftLanguageRuntimeImpl::AddModuleToReflectionContext(std::__1::shared_ptr<lldb_private::Module> const&) + 2766 5 LLDB 0x0000000123dc6d60 std::__1::__function::__func<lldb_private::SwiftLanguageRuntimeImpl::ProcessModulesToAdd()::$_0, std::__1::allocator<lldb_private::SwiftLanguageRuntimeImpl::ProcessModulesToAdd()::$_0>, bool (std::__1::shared_ptr<lldb_private::Module> const&)>::operator()(std::__1::shared_ptr<lldb_private::Module> const&) + 32 6 LLDB 0x00000001239bdad2 lldb_private::ModuleList::ForEach(std::__1::function<bool (std::__1::shared_ptr<lldb_private::Module> const&)> const&) const + 66 7 LLDB 0x0000000123dba72a lldb_private::SwiftLanguageRuntimeImpl::ProcessModulesToAdd() + 346 8 LLDB 0x0000000123dba0c9 lldb_private::SwiftLanguageRuntimeImpl::GetReflectionContext() + 57 9 LLDB 0x0000000123dd32e9 lldb_private::SwiftLanguageRuntimeImpl::BindGenericTypeParameters(lldb_private::StackFrame&, lldb_private::TypeSystemSwiftTypeRef&, lldb_private::ConstString) + 121 10 LLDB 0x0000000123dd3b8b lldb_private::SwiftLanguageRuntimeImpl::BindGenericTypeParameters(lldb_private::StackFrame&, lldb_private::CompilerType) + 347 11 LLDB 0x0000000123dc980d lldb_private::SwiftLanguageRuntimeImpl::GetSwiftRuntimeTypeInfo(lldb_private::CompilerType, lldb_private::ExecutionContextScope*, swift::reflection::TypeRef const**) + 621 12 LLDB 0x0000000123dcf9b1 lldb_private::SwiftLanguageRuntimeImpl::GetBitSize(lldb_private::CompilerType, lldb_private::ExecutionContextScope*) + 49 13 LLDB 0x0000000123dc332f lldb_private::SwiftLanguageRuntime::GetBitSize(lldb_private::CompilerType, lldb_private::ExecutionContextScope*) + 63 14 LLDB 0x0000000123fb0dd1 lldb_private::TypeSystemSwiftTypeRef::GetBitSize(void*, lldb_private::ExecutionContextScope*)::$_0::operator()() const + 689 15 LLDB 0x0000000123fb0aa8 lldb_private::TypeSystemSwiftTypeRef::GetBitSize(void*, lldb_private::ExecutionContextScope*) + 440 16 LLDB 0x0000000123aa9d61 lldb_private::CompilerType::GetBitSize(lldb_private::ExecutionContextScope*) const + 241 17 LLDB 0x0000000123aa9dc9 lldb_private::CompilerType::GetByteSize(lldb_private::ExecutionContextScope*) const + 9 18 LLDB 0x00000001239ef9e1 lldb_private::ValueObjectVariable::UpdateValue() + 241 19 LLDB 0x00000001239d9993 lldb_private::ValueObject::UpdateValueIfNeeded(bool) + 1011 20 LLDB 0x00000001239dac20 lldb_private::ValueObject::GetError() + 16 21 LLDB 0x0000000123868231 ValueImpl::GetSP(lldb_private::ProcessRunLock::ProcessRunLocker&, std::__1::unique_lock<std::__1::recursive_mutex>&, lldb_private::Status&) + 145 22 LLDB 0x000000012385cd28 lldb::SBValue::GetSP(ValueLocker&) const + 376 23 LLDB 0x000000012385dab9 lldb::SBValue::GetValueType() + 297 24 lldb-rpc-server 0x000000010f2f730a rpc_server::_ZN4lldb7SBValue12GetValueTypeEv::HandleRPCCall(rpc_common::Connection&, rpc_common::RPCStream&, rpc_common::RPCStream&) + 42 25 lldb-rpc-server 0x000000010f300749 rpc_common::Connection::PrivateHandleRPCPacket(rpc_common::RPCPacket&, rpc_common::RPCPacket&, bool&) + 1337 26 lldb-rpc-server 0x000000010f304434 Packets::ProcessPackets() + 564 27 lldb-rpc-server 0x000000010f30418a Packets::ReadThread() + 314 28 lldb-rpc-server 0x000000010f304049 Packets::RunReadThread(void*) + 9 29 libsystem_pthread.dylib 0x00007ff81847018b _pthread_start + 99 30 libsystem_pthread.dylib 0x00007ff81846bae3 thread_start + 15 Please file a bug report against lldb reporting this failure log, and as many details as possibleerror: Assertion failed: (LLDBMemoryReader module to address map ran into pointer authentication mask!), function addModuleToAddressMap, file /AppleInternal/Library/BuildRoots/603ae698-b099-11ef-b64c-aabfac210453/Library/Caches/com.apple.xbs/Sources/lldb/llvm-project/lldb/source/Plugins/LanguageRuntime/Swift/LLDBMemoryReader.cpp, line 537

Hello, I created a code in Xcode on my Mac. Once it was debugged I tried to run it on a simulator. Every time I run it on a simulator I get the white screen with the spinning red box. I'm very new at this and I am creating this app for my own child. As a teacher I couldn't stand the other math fact apps. You'll have to talk to me like an infant.

If you add a new string in your app (for example String(localized: "contact_support_message", defaultValue: "Please contact support")), then later you change that default value and rebuild, the string catalog updates to match as expected. But once that string is translated, changing the default value in code and rebuilding does not update the catalog. You seemingly have to go manually change the default value for English in the catalog to match the code (which marks the translation as Needs Review). Is there a better way? Or is there a way to determine what strings have default values in code that do not match the catalog values to see if any were missed as wording was tweaked over time?

Hello, Is there currently any workaround to install and run an iOS 14.x simulator on macOS 26? So far, I have checked Xcode 26.2, and the oldest simulator runtime available there appears to be iOS 15.0. I may be missing something, so I wanted to confirm if anyone has found a way to use iOS 14.x on this macOS version. Thank you.

Provisioning profile doesn't match the entitlements file's value for the com.apple.developer.nfc.hce.iso7816.select-identifier-prefixes entitlement. Although when we created the request, we added a list of AIDs which is the same as the list registered in Inof.plist <key>com.apple.developer.nfc.hce.iso7816.select-identifier-prefixes</key> <array> <string>XXXXXX</string> <string>XXXXXX</string> <string>XXXXXX</string> </array> How can we get a better message of diffs between them?

I saw this file among my project's check-in: .swiftpm/xcode/package.xcworkspace/contents.xcworkspacedata Does this need to be added to source control? Or the .gitignore file (or equivalent)? Or are there some files within the ".swiftpm" that should be checked in, and others ignored?

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

When using Team “57AWJ345M2” and setting the project’s Bundle ID to “com.marsgame.fg2”, enabling the iCloud capability and checking Key-Value Storage results in the following error:"Provisioning profile "iOS Team Provisioning Profile: com.marsgame.fg2" doesn't match the entitlements file's value for the com.apple.developer.ubiquity-kvstore-identifier entitlement." This issue does not occur if we use a different Team or a different Bundle ID. The project was transferred from another Team to this new Team, and everything worked fine before the transfer. Additionally, we have tried creating a brand new project, but as long as we use this same Team and this same Bundle ID, the error still occurs when enabling Key-Value Storage.

I've been developing an advanced gps tracking tool and had over 500 miles of data collected in the local storage of my test app. Recently, I used the XcodePreviews app to use my device to test UI updates as I was making them. To my surprise, doing this cleared all the data from my actual test app. Has this happened to anyone else before? Is there a way to recover my lost data? Why does this happen? I've verified that this is always clearing my app data. I tested by adding data to my actual test app then launching XcodePreviews - only to find that my app data has been cleared.

I’m running macOS 15.7 with Xcode 26.2, and I’m trying to learn the basics of AppKit. I’m fully aware that AppKit is considered a legacy / “old” technology and that Apple clearly does not promote it out of the box anymore. This is especially visible in recent versions of Xcode, where you can no longer create a macOS App template without Storyboards or SwiftUI. That said, AppKit is still widely used under the hood, so I think it’s reasonable to at least understand its fundamentals. Here’s the problem I’m facing. I create a standard macOS App project using the Xcode template (AppKit App Delegate). Then I: delete Main.storyboard remove all storyboard references from Info.plist try to create the window manually in applicationDidFinishLaunching At this point, the project builds, but the app either: does not show any window, or behaves as if it were not a proper GUI app While debugging, it looks like Xcode / Swift is treating my target more like a dylib / wrapper than a normal .app bundle (at least judging by runtime behavior and the lack of a proper AppKit lifecycle). While searching for answers, I found this article: https://ashidiqi.com/blog/how-to-setup-xcode-project-programmatically-with-appkit/ The author claims that in this scenario you must not use the @main attribute and instead need a main.swift file that manually calls NSApplicationMain. However, the article also mentions that Xcode shows the error: 'main' attribute cannot be used in a module that contains top-level code The confusing part is that I do not have any top-level code in my project when using @main. At the same time, when I ask an LLM for clarification, it tells me that: @main does not require a storyboard removing a storyboard does not force you to switch to main.swift @main should work fine for a fully programmatic AppKit app So I’m left with two concrete questions: What is the correct, modern answer here? When building a fully programmatic AppKit app (no storyboard, no SwiftUI), do you actually need main.swift, or is @main still fully supported and correct? Is there any supported or recommended way in modern Xcode to get a “clean” AppKit app template without a storyboard? Either via project settings, templates, or some documented workflow — without having to fight the build system or end up with a half-broken target. I’m not trying to fight Apple’s direction here — I just want to understand the correct way to work with AppKit in 2025, even if it’s not the preferred path anymore. Thanks in advance for any clarification.

**The issue - ** I can't add "In-App Purchase" as a capability in xCode to my iMessage extension target. **What I have tried - ** I have a valid provisioning profile with In-App Purchases enabled. I have agreed to all agreements in the apple developer console. I have an apple developer membership. I have added an active bank account to my apple developer account. **How the issue came to be - ** I am trying to develop a "stand-alone" iMessage app (no underlying app) which as I understand it is different from a "iMessage extension app"(this has an underlying app that it syncs/interacts with). To do this, I updated my mac to latest OS (Tahoe 26.2) and xCode as well. I then began by using the "iMessage App" template in xCode. And BAM right off the bat, I could not get the "In-App Purchases" capability to show up when I select my iMessage extension target. To be clear, when you make the template, you get 2 targets, one is just a regular "app" target and the other is the iMessage extension target. Now I am not sure if I even need the "app" target if I'm trying for a standalone iMessage app, but I figured it wouldn't be causing this issue as I have tried deleting that target and nothing changed. **Replicating the issue - ** I have tried creating other "iMessage App"'s off of the template to see if maybe I just got it wrong or misconfigured something in my development, but it seems like when you start one of those templates, you immediately are not able to see the "In-App Purchase" capability. **Help! - ** I know this to be possible as there is another (very popular) iMessage extension out on the app store right now called "Game Pigeon" which is also provided by an individual just like I am trying to do, and he uses In App Purchases in his iMessage app. Any help on this would be GREATLY appreciated. Please reach out to me if you need/want additional info or could/want to schedule a meeting.

Without this, I can't install/open Unreal Engine on my iMac OS 26.2 Tahoe. I can't even download the Metal Toolchain in Xcode-Settings-Components. It fails every time. when I try to open Unreal Engine, it says this: Xcode Metal Compiler error: error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain But every time I try to download Metal Toolchain in terminal, it says this: xcodebuild: error: Failed fetching catalog for assetType (com.apple.MobileAsset.MetalToolchain), serverParameters ({ RequestedBuild = 17C48; }) % sudo xcode-select --reset xcrun -f metallib Password: xcrun: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find metallib 2> /dev/null' failed with exit code 17664: (null) (errno=No such file or directory) xcrun: error: unable to find utility "metallib", not a developer tool or in PATH

I downloaded package, I can see it in Package Dependencies tab, [swift-collections | https://github.com/apple/swift-collections.git | Up to Next Major Version] — looks OK. But (quite strange): import Collections //🛑 No such module 'Collections' typealias Objects = OrderedSet<anyHashable> // No error I took Collection word from a list or typed — no difference. if I remove import Collections there is no OrderedSet anymore (of course) Can't compile. Cleaned build folder, restarted Xcode... What could be wrong with it? Any ideas?