Hi, I have listed below the Feedbacks for Xcode 27, please have a look at it, considerable time was spent on filing these feedbacks, thanks! Environments All of them were tested on the environment: macOS 26.5.1 (25F80) Xcode 27.0 beta (27A5194q) Feedbacks FB23133706 (Git stage tab) FB23132869 (markdown - code block) FB23132403 (markdown - search) FB23078039 (stash - slow / unresponsive) FB23077930 (stash - allow multiselection) FB23055381 (Run destination - Clear recents) FB23041713 (SwiftUI preview - SwiftData) FB23033844 (Bundle ID) FB23033231 (Device Hub - sizes)

I just upgraded MacOS to Tahoe 26.6.1, and upgraded XCode too. Then Xcode crashes on every launch and is completely unusable. Translated Report (Full Report Below) ------------------------------------- Process: Xcode [1718] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 26.6 (24959) Build Info: IDEApplication-24959000000000000~2 (17F113) Code Type: ARM-64 (Native) Role: Background Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [917] User ID: 502 Date/Time: 2026-08-13 11:26:33.1318 +0800 Launch Time: 2026-08-13 11:26:33.0308 +0800 Hardware Model: Mac16,8 OS Version: macOS 26.6.1 (25G76) Release Type: User Crash Reporter Key: ED18B1CA-EA9C-0657-0CF1-1EFA8C60919E Incident Identifier: 8350CBBA-0B41-4A77-B262-CD0662709FB1 Time Awake Since Boot: 47 seconds System Integrity Protection: disabled Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6, Abort trap: 6 Terminating Process: Xcode [1718] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x1843745e8 __pthread_kill + 8 1 libsystem_pthread.dylib 0x1843af8d8 pthread_kill + 296 2 libsystem_c.dylib 0x1842b5978 abort + 148 3 libsystem_c.dylib 0x1842b5a94 abort_report_np + 84 4 Xcode 0x102624ed0 main.cold.1 + 36 5 Xcode 0x102624e1c main + 340 6 dyld 0x183fe44e4 start + 6992 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000000000073 x5: 0x000000000000002e x6: 0x000000016d7db278 x7: 0x0000000000000000 x8: 0x61cbe9e2533f85e8 x9: 0x61cbe9e3a3e16468 x10: 0x0000000000000002 x11: 0x00000000fffffffd x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000000 x16: 0x0000000000000148 x17: 0x00000001f242f400 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000000103 x21: 0x00000001f0dee260 x22: 0x0000000102d5cbe0 x23: 0x00000001f0df5908 x24: 0x0000000000000001 x25: 0x000000016d7db6d0 x26: 0x00000001f0defa70 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x000000016d7db3f0 lr: 0x00000001843af8d8 sp: 0x000000016d7db3d0 pc: 0x00000001843745e8 cpsr: 0x40000000 far: 0x0000000000000000 esr: 0x56000080 (Syscall) Binary Images: 0x102624000 - 0x102627fff com.apple.dt.Xcode (26.6) <8025d4bb-71ea-3f57-bade-2e3c847b6cf3> /Applications/Xcode.app/Contents/MacOS/Xcode 0x18436b000 - 0x1843a82e7 libsystem_kernel.dylib (*) <7cfb3a10-adb2-32c4-99b5-922a111b3224> /usr/lib/system/libsystem_kernel.dylib 0x1843a9000 - 0x1843b5b3b libsystem_pthread.dylib (*) <12342372-0084-37a5-9ea6-2e4dc940c685> /usr/lib/system/libsystem_pthread.dylib 0x18423d000 - 0x1842be1e7 libsystem_c.dylib (*) <fdc4e366-5c14-3a1e-bc35-d933d28cdcf3> /usr/lib/system/libsystem_c.dylib 0x183fc4000 - 0x1840774ff dyld (*) <df42dd9d-ad11-33a7-8849-9ad5df30a274> /usr/lib/dyld 0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

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.

[Q] Is it a known issue that the Xcode static analyzer hallucinates past results? Basically, the issue I've been observing for a few releases of Xcode now (including 27b) is that if you run a static analysis, fixes the reported issues and re-run a static analysis, you will get exactly the same results as with the first run. It's as if Xcode did not take into account the fixes. If you clean the builds (cmd + shift + K), and run the analysis again, this time, you will get up-to-date results.

I've been trying for months to get Gemini 3.5 Flash to work with Xcode 27 Beta (1-3) agentic coding but have failed. Xcode currently uses Gemini CLI v0.42.0 from last year, so it can't call Gemini 3.5 Flash even though all that needs to change is a few characters in the API call. Gemini users are currently forced to choose between 3.1 Pro and 3.1 Flash Preview--both weren't the best choices two months ago, but with the release of 3.6 Flash which is better at coding that 3.1 Pro and miles cheaper, these choices are now unsuitable for any serious workload. I live in Hong Kong, where OpenAI and Anthropic services aren't offered, so Google is the only (native) AI provider for Xcode agentic coding. The cost issue from funneling all the work into 3.1 Pro is terrible especially with some agent bugs that have yet to be ironed out. Given Apple's close partnership with Google on AI, I'm genuinely surprised that after 4 Betas we're still using a Gemini CLI from 2025 that forces users to choose between two very unappealing models. Xcode is basically forcing Google users to switch to OpenAI/Anthropic. Questions: I'd like to know if this will be fixed soon and whether Google users should expect slower updates (i.e. be forced to use older models). Does anyone know of any workarounds?

In Xcode 27 Beta 4 (27A5228h), building a project that has a SwiftPM binary target (xcframework) linked directly from both an app target AND a framework target that is embedded in that app fails with "Multiple commands produce" errors. The same project and pbxproj builds successfully in Xcode 27 Beta 3 (27A5218g), so this is a regression introduced in Beta 4. Steps to Reproduce Create a new iOS App project. Add a Framework target (e.g. "SampleCommon") and embed it into the app. Add a SwiftPM dependency for a package that vends a binary xcframework product. Confirmed with airbnb/lottie-spm 4.6.1 (https://github.com/airbnb/lottie-spm). In "Frameworks, Libraries, and Embedded Content" of the app target, add the SwiftPM product (Lottie) with "Embed & Sign". In "Frameworks and Libraries" of the framework target, add the same SwiftPM product (Lottie). Build the app scheme for iOS Simulator. Expected result Build succeeds. The xcframework is embedded exactly once into the .app bundle. This is the behavior in Xcode 27 Beta 3 and Xcode 26. Actual result Build fails with: error: Unexpected duplicate tasks error: Multiple commands produce '.../<App>.app/Frameworks/Lottie.framework/Lottie' error: Multiple commands produce '.../<App>.app/Frameworks/Lottie.framework' Two Copy tasks are emitted for the same output path in the app target: Copy from Build/Products/Debug-iphonesimulator/PackageFrameworks/Lottie.framework Copy from SourcePackages/artifacts/lottie-spm/Lottie/Lottie.xcframework/ios-arm64_x86_64-simulator/Lottie.framework Additionally, an auto-generated target named "Lottiedynamic-product" emits duplicate MkDir / ProcessInfoPlistFile tasks for PackageFrameworks/Lottie.framework, which suggests the packaging path for binary xcframework products has been duplicated in Beta 4. Regression Xcode 27 Beta 3 (27A5218g): builds successfully Xcode 27 Beta 4 (27A5228h): fails with the above errors Xcode 26.x: builds successfully Minimal reproduction The issue reproduces on a 2-target Xcode project (app + framework) with airbnb/lottie-spm added and linked from both targetstory captures the smallest triggering diff: pattern1: app links Lottie only -> BUILD SUCCEEDED pattern2: framework links Lottie only -> BUILD SUCCEEDED pattern3: both app and framework link Lottie -> BUILD FAILED (only on Beta 4) Only the framework target's packageProductDependencies and Frameworks build phase entries differ between the succeeding and failing states. Workaround Link the SwiftPM binary product from only one target (either the app or the framework, not both). If only the framework tarl gets the framework transitively at runtime. Impact Any project that uses a SwiftPM binary xcframework and organizes code across multiple linked targets (a very common pattern for larger apps) is blocked from adopting Xcode 27 Beta 4. Environment Xcode 27.0 Beta 4 (27A5228h) macOS 26.5.2 Package: airbnb/lottie-spm 4.6.1 Destination: iOS Simulator (iPhone 17, latest)

I am experiencing an App Store submission issue after updating my Mac development environment. A build of my iOS app can be uploaded and appears in App Store Connect/TestFlight, but when I try to use the build for App Review, it is rejected because it was built using a beta version of Xcode. I am currently using Xcode 27 beta because of the macOS environment installed on this Mac. I have been advised that I may need to return the Mac to a stable macOS/Xcode environment and rebuild the app. This is particularly concerning because the app and its development data already exist on this Mac, and reverting the development environment may require a full backup and OS reinstallation. I would like to know: What is the officially supported procedure to return to a stable macOS and Xcode environment without losing development data? Which stable Xcode version should be used to rebuild the app for App Store submission? Is there any supported way to submit the existing build, or must it be rebuilt completely with a non-beta Xcode? I would also like to know whether other developers using the current beta environment are experiencing the same App Store Connect submission restriction. I would also like clarification regarding responsibility and remediation in this situation. If a development environment provided through Apple’s software update or beta distribution results in an existing application becoming unable to be submitted to App Store Connect, what responsibility does Apple assume for the resulting disruption to developers? In particular, if resolving the issue requires backing up development data, reinstalling macOS, reinstalling Xcode, and rebuilding the application, does Apple provide an official recovery procedure or support for developers affected by this situation? I believe this is important not only for my application, but also for other developers who may encounter the same issue. I would appreciate an official clarification from Apple regarding both the technical solution and Apple’s policy for developers affected by this problem. Thank you.

I would like to be able to use an SPM registry to access the various open source packages that my app uses. I want to do this so that I can use JFrog's Artifactory as a registry proxy, and manage my app's dependencies through it. I've found an announcement in 2019 that GitHub Package Registry was going to support Swift packages, but I have found no newer info. All the other things I've found which call themselves Swift package registries do not conform to SE-0292. Are there any public SPM registries? Will there be any in the near future?

After upgrading to Xcode 16 and iOS 18 SDK, my Objective-C project has serious BOOL value errors only on iOS 18 Simulator. The same code works perfectly on real iPhone devices and Mac Catalyst. When getting BOOL return values from methods or assigning system API results to BOOL properties, it generates unexpected negative large numbers. Since C language treats all non-zero values as true in if() judgment, our business logic is completely broken. Could you please explain what underlying changes in iOS 18 Simulator or Xcode 16 compiler caused this BOOL parsing problem? Thank you.

I’m seeing a consistent Instruments error after recording a SwiftUI profile: “Failed to stop recording session: Data Providers emitted errors: Required” The recording itself starts and runs normally. The error appears only after I stop recording, while Instruments is processing the trace. No profiling results are produced. Environment: Xcode 27.0 beta 5 (27A5237l) Instruments 27.0 (27A5237l) Physical iOS device running the latest beta I can reproduce this consistently using the SwiftUI template. I’ve also tried updating Instruments and restarting the tools, but the issue remains. Expected: The trace finishes processing and displays the collected data. Actual: Processing fails with the data-provider error above.

I use my fingerprint to attempt to log in, but the spinner just spins and a file is downloaded to my Download folder with the title icloud.developer.apple.com with zero bytes. I've cleared cookies and cache, but it doesn't help. I can get to CloudKit Dashboard via Xcode in the Signings and Capabilities tab, but I never had to do it this way. I've been doing it via the Mac.

Seems like there is an issue in Xcode 27 beta 4 & 5 where DeviceHub doesn't show iOS 16 devices or simulators. I've checked the filters to ensure I haven't hidden anything and the are listed in the Xcode destination dropdown.

Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says "Not Signed In". I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574

I'm unable to use the Claude Agent in Xcode 26 (stable release) running on macOS 27 beta 5. Steps to reproduce: Open Xcode 26 Settings > Intelligence Select Claude Agent Expected: The Account section loads and allows me to sign in / manage my Claude account. Actual: The Account row shows a loading spinner indefinitely and never resolves, so I can't sign in or use the Claude Agent at all. Environment: Xcode 26 (stable), macOS 27 beta 5. Is this a known incompatibility with macOS 27 beta 5? Is there a workaround (e.g. clearing a cache or re-adding the account) to get the Claude Agent account section to load?

My app start up has became horrid. It takes 1 minute to open SQLlite database for my rust core. Impossible to work... I have Address Sanitizer, Thread Perf Checker and Thread Sanitizer disabled...

I’m seeing a reproducible issue in both Xcode 26 and Xcode 27 where Coding Assistant appears to stop autocompleting when a project contains a larger number of Swift Package dependencies. Symptoms: Autocomplete suggestions from Coding Assistant stop appearing. File targeting with @ stops working. The issue typically appears shortly after opening the project If I start a brand-new chat immediately after opening the project, Coding Assistant sometimes works briefly before failing Reducing or removing Swift Package dependencies fixes the issue I’ve created a sample project that reproduces the problem and have also filed Feedback Assistant report: FB23341243 The issue seems related to package count or project complexity rather than any specific package, although I haven’t yet identified the exact threshold that triggers it. Has anyone else run into this or has anyone found a workaround?

Hi, I am unable to sign into the sandbox account on the simulator. Settings > Developer > Sandbox Apple Account > Sign in Xcode: 26.6 (17F113) Xcode Simulator: 16.0 (1063.4) I have even tried on Device Hub on Xcode 27. I vaguely remember being able to sign into the simulator using Questions: Is anyone able to sign into Sandbox account on the simulator / device hub? Is there any workaround? Is this a known issue?

Recently, with Xcode 26.6, we've been unable to install apps on some physical devices (iPhone, iPad). Some devices work fine. An alert saying "Install Application not available" appears. I reported it through Feedback Assistant, but someone from Apple replied that it's an issue with Xcode 27.0 beta and told me to install the latest Xcode 27. However, I'm actually using Xcode 26.6. The issue is still unresolved, so if anyone learns anything, I'd appreciate it if you could share an update.

I am trying to upgrade my app to use Xcode 26 and I cannot get my tests to launch. I am trying to launch tests to the simulator, and I always get this error after 300 second timeout: "encountered an error (The test runner hung before establishing connection.)" There are no other errors getting logged. I can run to the same simulator just fine, and in Xcode 16 the tests launch with no issues. The tests also run fine on an actual iPhone. Thanks in advance.

Everything has been updated. Countless reboots and reinstalls. Yet Xcode still won't open. Keep getting "Xcode quit unexpectedly dialog" with buttons to Reopen, Ignore, Report. Any suggestions on what lingering file is killing Xcode on open? Thanks!