Summary: After upgrading to Xcode 26.4, app-hosted XCTest execution on physical devices running iOS 16 fails at test-planning time with "Logic Testing Unavailable." The same project and same device work under Xcode 26.2. The failure reproduces with a standalone minimal Xcode project, which suggests this is an Xcode regression rather than a project-configuration issue. Environment: Xcode: 26.4 (17E192) macOS: Tahoe 26.4 Failing device: iPhone 11 (iPhone12,1), iOS 16.0.3 Working comparisons: Xcode 26.2 + same iPhone 11 (iOS 16.0.3): works Xcode 26.4 + iPad Pro 11-inch (4th generation) on iOS 26.3: works Regression: Yes. Works on Xcode 26.2. Fails on Xcode 26.4. Same project, same signing setup, same physical iOS 16 device. Minimal reproduction: A minimal sample project with: one iOS app target one app-hosted unit-test target one UI-test target (for comparison; not required to reproduce) Steps for the unit-test repro on a physical device running iOS 16: Build for testing: xcodebuild -project TestProject.xcodeproj \ -scheme TestProject-UnitTests \ -sdk iphoneos \ -destination 'platform=iOS,id=<DEVICE_UDID>' \ -derivedDataPath DerivedData-Device-Unit \ -resultBundlePath Results-Device-Unit-Build.xcresult \ DEVELOPMENT_TEAM=<TEAM_ID> \ CODE_SIGN_STYLE=Automatic \ build-for-testing Run tests without building: xcodebuild -project TestProject.xcodeproj \ -scheme TestProject-UnitTests \ -sdk iphoneos \ -destination 'platform=iOS,id=<DEVICE_UDID>' \ -derivedDataPath DerivedData-Device-Unit \ -resultBundlePath Results-Device-Unit-Test.xcresult \ DEVELOPMENT_TEAM=<TEAM_ID> \ CODE_SIGN_STYLE=Automatic \ test-without-building Note: xcodebuild test (combined build and test) also fails with the same error. Expected result: The hosted unit tests run successfully on the connected physical device, as they do under Xcode 26.2. Actual result: Step 1 (build-for-testing) succeeds. Step 2 (test-without-building) fails immediately (within ~1 second) with: 2026-03-26 11:23:28.683 xcodebuild[51930:731004] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. 2026-03-26 11:23:28.725 xcodebuild[51930:730966] [MT] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. 2026-03-26 11:23:29.239 xcodebuild[51930:730966] Writing error result bundle to /var/folders/jl/knmkq18x4cg_3w087zgpfldm0000gn/T/ResultBundle_2026-26-03_11-23-0029.xcresult xcodebuild: error: Failed to build project TestProject with scheme TestProject-UnitTests.: Cannot test target “redacted” on “redacted”: Logic Testing Unavailable Logic Testing on iOS devices is not supported. You can run logic tests on the Simulator. Why this looks like an Xcode regression: The same project and same physical iOS 16.0.3 device work under Xcode 26.2. Under Xcode 26.4, build-for-testing still succeeds, so signing, provisioning, and bundle construction appear valid. The failure happens only when Xcode plans or launches the on-device test run. Before the failure, Xcode 26.4 logs: DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. A newer physical device running iOS 26.3 works under Xcode 26.4 without this warning. The issue also reproduces with a minimal standalone Xcode project, which makes a project-specific configuration problem unlikely. The Xcode-generated .xctestrun files for the passing Xcode 26.2 case and failing Xcode 26.4 case are structurally equivalent, making an .xctestrun format difference unlikely to be the cause.

Hello! I have windows pc and an iphone, I want to develop apps and use xcode... Please help me on that and what should I doThank YOU !

Environment: MacBook Air M4 macOS 27 Golden Gate Beta Xcode 27 Beta iPhone running iOS 27 Beta Apple Watch paired to the iPhone Steps to Reproduce: Install macOS 27 Beta and Xcode 27 Beta. Pair an Apple Watch with an iPhone running iOS 27 Beta. Enable Developer Mode on the iPhone. Connect the iPhone to the Mac and launch Xcode. Open Window → Devices and Simulators. Attempt to locate the paired Apple Watch or enable Developer Mode on the watch. Expected Result: The paired Apple Watch appears in Xcode for development purposes. A Developer Mode option is available on the Apple Watch. Xcode is able to recognize and communicate with the watch through the paired iPhone. Actual Result: The Apple Watch does not appear in Xcode. No Developer Mode option is visible on the watch. The iPhone is successfully paired and running iOS 27 Beta, but the watch remains unavailable for development workflows. Additional Notes: The iPhone and Apple Watch are already paired and functioning normally. Developer Mode is enabled on the iPhone. Restarting devices and reconnecting the iPhone did not resolve the issue. Unsure whether this is a limitation of the current beta builds or a regression in Xcode/watchOS development tooling.

Overview On Xcode 27, when trying to run on a specific destination, the option to “Clear Recent” is missing. This was available in Xcode 26. Manage Devices option exists, but this is to permanently add / remove destinations, this is different from “Clear Recent”. Please bring back “Clear Recent” (from Xcode 26 to Xcode 27) option to Xcode as it is very useful Environment: macOS 26.5.1 (25F80) Xcode 27.0 beta (27A5194q) Feedback FB23055381

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)

Filed a feature request in feedback assistant, but starting a discussion here as well since I'm probably not the only one. The issue I have is that coding assistant and previews seem to be mutually exclusive. That means that when I'm iterating on UI, I either have to rely on the coding assistant showing me preview screenshots (cannot interact), firing up Device Hub (have to manually kick off a build after each change) or manually opening the associated preview (requires a lot of hoping back and forth). This feels inefficient and means I have to hop around and manage my windows and tabs more. A slight work around is to open a split view with the file and preview there. This layout is inefficient and clunky. I would love if Xcode supported a pinned preview next to coding assistant (or automatically showed the relevant one). I imagine this working just like showing a preview next to a file cmd + opt + return hides/shows the preview. FB23219611

Hi I have a problem downloading the iOS simulator, I have a slow internet connection. Is there some way I can get a direct download link to the 7GB DMG image. To donload on a local nearby server? Please Help

Currently running PacketLogger 15.4 with Sonoma 14.6.1 on a 2020 M1 Macbook Pro and am trying to log packets for a custom bluetooth device I have designed. I have used packetlogger in the past for the same device on this same laptop and had no issues seeing all advertised bluetooth packets from what seemed like every device in the office. It has been a few months and certainly a couple of OS updates but Packetlogger does not seem to log any packets at all anymore. I have made sure to clear all filters and to ensure I get all forms of bluetooth traffic. I have reinstalled the xcode developer tools as well and this has made no difference. I can clearly see the bluetooth advertising packets from my device using a ble scanner on my phone. Even trying to connect my phone over bluetooth to my laptop does not result in any logs. I am happy to provide more information as well as screenshots if need be. Thank You!

I don’t have a plus sign next to build in my app developer account page, so I can’t upload my app or send it in for review… anyone have this happen to them? Any solutions besides wait for them to fix it internally?

First of all: I love the Xcode implementation of agents. Even right out the gate it works really well on regular projects. However it's rough around the edges--it's beta 1 after all, and I've been prodding around the permissions section. My configuration: macOS 26.5.1, Gemini 3.1 Pro agent via Gemini Enterprise Agent Platform Things were working fine until I got nervous about the agent downloading things using google_web_search and web_fetch since I expected the agent to do that in the cloud but apparently it's automatically downloading stuff to my device, so I disabled those tools out of caution. Later I stumbled upon the skills documents in /Users/USERNAME/Library/Developer/Xcode/CodingAssistant/gemini/.gemini/GEMINI.md which basically tells the agent to: ...take special care to avoid using command line tools like ls or find just to learn basic information about the project or its contents. The user may be prompted to approve every single one of those command line invocations, so it's best to use them sparingly. So I said "Why not?" and deleted the rest of the permissions for better security--you never know what a beta 1 agent might do, and the text implies the worst that'll happen is they'll ask for permission. Now my agent permissions page is empty. After I did that I noticed my agent no longer works in the library project I've been working on. It can't read project files at all, even though things were fine before. Strangely, the agent works just fine in a regular app project--it's just acting up in the library project. Here's a sample of the verbose output: Thinking: I'm currently examining the workspace path provided, which appears to differ slightly from the actual file structure I'm encountering within the PROJECTNAME directory. I'm trying to reconcile this discrepancy. I've realized the paths provided are Xcode workspace-relative and require specific Xcode tools for interaction. I was attempting direct file system access, which is incorrect. I will now attempt to use the appropriate mcp_xcode-tools commands, similar to how I successfully used XcodeLS earlier, to access these files within the project context. I attempted to use mcp_xcode-tools_XcodeRead, but it wasn't recognized. It seems the Xcode tools are not available in my current Plan Mode environment, which is perplexing given previous successful usage. I need to investigate this discrepancy further. AgentLS: The tool failed with no output. Thinking: I'm currently examining the contents of the /Users/USERNAME/Documents/PROJECTNAME/.swiftpm/xcode directory to understand the project structure. OBJECTNAME: 0 items Thinking: I'm currently trying to figure out the best way to access the swift-markdown and MarkdownView source files. It seems they're presented as workspace-relative paths, so I'll need to use the Xcode-specific tools like XcodeRead and XcodeGrep to interact with them. I'm trying to ascertain the precise names of the swift-markdown and MarkdownView source files, as they appear to be workspace-relative. I'm considering invoking the generalist agent, as the mcp_xcode-tools_XcodeRead tool might not be directly available to me at this level, and I need to confirm its accessibility. Note how it successfully used XcodeLS earlier but is now failing. Even if ls is allowed, it still fails. Reinstalling doesn't fix the issue, so I'm stuck without agent support for this library project. Other issues I've noticed Rolling back agent-made changes is painful, slow, and expensive when it really shouldn't be (just undo what was done instead of telling the agent to undo) Agent made changes are often not given rainbow highlights as they should Artifacts don't always show up Please don't make me manually toggle "verbose" every time I open a conversation. If it's not already obvious, I just like verbosity. I'd love to learn more about the Xcode agent tools available to the agent but there seems to be a lack of documentation anywhere. I've been resorting to extracting stuff from /Users/USERNAME/Library/Developer/Xcode/CodingAssistant/gemini/.gemini/ but those are skills, not tools. Still, it's a fantastic resource for a budding developer! I tried to repopulate my agent command permissions to see if that's the cause, but aside from ls, head, tail, grep, pwd, I don't know what else belongs there and reinstalling doesn't repopulate it. There's also no reset button.

I'm unable to reset simulators using the menu or the xcrun simctl tool: <output of xcrun simctl list> == Devices == -- iOS 17.5 -- iPhone SE (3rd generation) (5A06623A-173D-4C96-8DD3-3E9FE39A06F1) (Shutdown) iPhone 15 (iOS 17.5) (F4329E8D-29BB-4EA7-8465-C11A98D04ED7) (Shutdown) -- iOS 18.0 -- iPhone SE (3rd generation) (2DDE8F03-F8E1-4C1B-8E28-CD9B208F3FFA) (Shutdown) iPhone 16 Pro (DE788688-8AC6-40A0-B25C-A56AA423798E) (Shutdown) iPhone 16 Pro Max (1405184C-36A9-40F3-B0D0-4EEB88452883) (Shutdown) iPhone 16 (0CBBA7DB-B20E-4F17-BBC5-910F1F6E1A0A) (Shutdown) iPhone 16 Plus (95421C27-11A0-4FCF-A889-DAAE8557B271) (Shutdown) == Device Pairs == ~/Library`` ❯ xcrun simctl erase 0CBBA7DB-B20E-4F17-BBC5-910F1F6E1A0A An error was encountered processing the command (domain=NSCocoaErrorDomain, code=513): “data” couldn’t be moved because you don’t have permission to access “Deleting-8FEDFF47-5B2F-4534-BCA2-036BBE68CE37”. You don’t have permission. To view or change permissions, select the item in the Finder and choose File > Get Info. Underlying error (domain=NSPOSIXErrorDomain, code=1): The operation couldn’t be completed. Operation not permitted Operation not permitted Xcode Version 16.0 (16A242d) MacOS 15.0.1 (24A348)

Anyone else seeing a lot more "Class X is implemented in both ..." warnings on Xcode 27 than on Xcode 26? Same source, same flags, the count goes from a handful to a couple thousand, and some now correlate with real crashes (cast failures, missing protocol conformances) instead of the usual harmless first-wins behavior. Is this a known change in Swift 6.4 / Xcode 27? Is there a new flag I should be passing? Any suggestions welcome.

PLATFORM AND VERSION iOS Development environment: Xcode 26.4.1 (17E202) (or Xcode26.3 and Xcode26.5), macOS 26.4.1 (25E253) Run-time configuration: iOS iOS12.5.7 DESCRIPTION OF PROBLEM Applications built with Xcode 26 fail to launch on iOS 12 devices. The application installs successfully, but terminates immediately after launch. The application does not reach application startup code, including application:didFinishLaunchingWithOptions:. The same project, source code, build configuration, and deployment target work correctly on the same iOS 12 devices when built using Xcode 16. This issue appears to be related to binaries generated by Xcode 26 and is reproducible across multiple builds and devices running iOS 12. We would like to confirm whether iOS 12 is expected to remain supported when building applications with Xcode 26 and whether this behavior is a known issue. STEPS TO REPRODUCE Open an existing iOS application project. Set the deployment target to iOS 12.x. Build and archive the application using Xcode 26. Install the application on a physical device running iOS 12.x. Launch the application.

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?

Is anyone else finding model switching a bit disruptive during longer coding sessions? As we start using different models for exploration, implementation and review, having to go through settings interrupts the workflow. I would love to see model and reasoning controls directly inside the Coding Assistant UI.

I started a project targeting macOS and used Storyboard app lifecycle. I also used Xcode Previews in this project. If I: Keep the entry point of the main storyboard to a window controller. (as default setup in macOS), Turn the Xcode window into full-screen, That window controller would pop up its window every time Xcode Previews refreshes. I tested in Xcode 26.3 RC and many versions before.

On iOS 26.5 simulator runtime, running UI tests via xcodebuild test from the command line does not push the scheme's StoreKitConfigurationFileReference to the destination simulator's storekitd AppGroup Octane container. As a consequence, SKTestSession(configurationFileNamed:) either silently falls through to the production App Store (surfacing a "Sign in to Apple Account" SpringBoard alert during paywall tests), or throws SKInternalErrorDomain Code=3 "Error saving configuration file" if you call any SKTestSession instance method. The same project, same scheme, same .storekit file works correctly when launched via Xcode IDE (Cmd+R / Cmd+U) — which uses DVTDevice.handleStoreKitConfigurationSyncForBundleID:configurationFilePath: via an internal IDELaunchSession XPC path that the public xcodebuild CLI does not invoke. This regression makes StoreKit Test unusable in CI for any project using xcodebuild test or xcodebuild test-without-building against an iOS 26.5 simulator. Environment macOS: 26.x Xcode: 26.4.1 (25E253) iOS Simulator runtime affected: 26.5 iOS Simulator runtime that does not exhibit the bug: 26.1 Test target: XCTest UI tests Test plan: *.xctestplan with "storeKitConfiguration": "MyApp.storekit" in defaultOptions Affected scheme actions: Test (CLI) Not affected: Run, Test (Xcode IDE) Steps to Reproduce Create a SwiftUI iOS app com.example.MyApp. Add a MyApp.storekit with one auto-renewable subscription. Add a UI test target. In the xctestplan: defaultOptions.storeKitConfiguration = "MyApp.storekit". In the UI test base case: private var storeKitSession: SKTestSession? override func setUpWithError() throws { storeKitSession = try SKTestSession(configurationFileNamed: "MyApp") app.launch() } Boot a fresh iOS 26.5 simulator. Run via CLI: xcodebuild test \ -project MyApp.xcodeproj \ -scheme MyApp \ -testPlan MyAppUITests \ -destination "platform=iOS Simulator,name=iPhone 17 Pro" In the test, trigger paywall and call Product.purchase(). Expected Product.purchase() presents the StoreKit Test sheet labeled "[Environment] Xcode". Same behavior as Xcode IDE Cmd+U. Actual Production App Store flow triggers. SpringBoard alert "Sign in to Apple Account" appears. Tests waiting on the "Xcode"-labeled sheet fail with Element does not exist. Evidence The simulator's ~/Library/Developer/CoreSimulator/Devices/<UDID>/data/Containers/Shared/AppGroup/<storekit-AGID>/Documents/Persistence/Octane/com.example.MyApp/Configuration.storekit: Present (≈100 KB) when launched via Xcode IDE. Missing when launched via xcodebuild test CLI on the same simulator UDID. Workarounds Attempted (all fail on iOS 26.5) No-op XCTestCase "warmup" that calls XCUIApplication.launch() + sleep — does not trigger the sync because XCUIApplication.launch() routes through XCTRunner, not IDELaunchSession. Multi-destination xcodebuild test with -parallelize-tests-among-destinations. Manually cp-ing the .storekit file into the AppGroup Octane container — storekitd only loads via the XPC channel. launchctl kickstart -k system/com.apple.storekitd — wipes in-memory state, does not pick up disk file. Only working workaround: open project in Xcode IDE, Cmd+R, wait ~20–30 sec, Cmd+., then Cmd+U. Not viable for CI. Related Open Feedback FB22237318 — SKTestSession instance methods (clearTransactions(), failTransactionsEnabled = true) throw SKInternalErrorDomain Code=3 "Error saving configuration file". Discussion thread: https://developer.apple.com/forums/thread/808030 The iOS 26.5 Release Notes (https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-26_5-release-notes) under StoreKit Test list this issue as resolved in 26.5: "Fixed: SKTestSession may fail to save its configuration file when invoked outside of an Xcode debug session." However, on the public iOS 26.5 simulator runtime the behavior is unchanged — SKTestSession still hits Code=3 on any mutation, and xcodebuild test from CLI still does not sync the .storekit configuration. The 26.5 fix either did not actually ship, or this report describes a distinct but related issue that the fix did not cover. Impact Any CI/CD pipeline running UI tests for apps with StoreKit subscriptions is broken when targeting an iOS 26.5 simulator. Workarounds are either: Pin CI simulator runtime to iOS 26.1. Manually run the project in Xcode IDE before each test run (impossible headless). Has anyone found a CLI-friendly workaround? Or is there an undocumented xcodebuild flag / simctl command that can trigger the same DVTDevice sync from outside the IDE?

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

FB22844728 Xcode 26.5, macOS 26.5, MacStudio M1 64 GB The disaster of S-L-O-W T-Y-P-I-N-G that plagued Xcode several years ago returns. I guess all the ultra-advanced LLM neuroneirowebs still can't advise those at Apple who develop the Xcode app how to provide this uber-exotic, unheard-of functionality: JUST TYPING THE CODE. This disaster doesn't affect all projects, but it does affect the exact one I'm working on, and I need to type a lot of code there. Significant time is already wasted. I performed all the recommended steps like relaunching, restarting, and deleting deprived data with no effect. Hope something can be done about it..

I am building an interactive application. My application architecture looks like this: There will be a LoaderBinary that will load 1 or more shared libraries (.framework in this case). This is also where the entry point from an OS perspective lies. There will be 1 or more frameworks built. This framework is expected to have large part of my logic as shared code so that multiple flows like the application flow, widget, notifications etc can reuse code by loading this framework itself. Now, I want to achieve the following: Building a framework independently - I believe this is doable and works fine too. Building a mach-o binary - This is what we are not clear if it is allowed or not to build just a mach-o binary ? Yes, there is an option to build a command-line tool but as this is an interactive binary, what should be the path to take ? Building a macOS bundle (.app) using 1 and 2 - Now, as I have a PRE-BUILT framework and a PRE-BUILT mach-o binary, can I create a application bundle using these ? Some directions here will help to take this forward - in alignment with both my architecture as well as how Apple Build system works. Thanks!