Xcode 26.3 MCP xcode-tools: RunSomeTests / RunAllTests response violates tool output schema (missing required errors per test) I’m using the MCP server “xcode-tools” shipped with Xcode 26.3 to run tests. Two tools fail consistently due to a schema mismatch: RunSomeTests RunAllTests Steps Call XcodeListWindows and get a valid tabIdentifier for my workspace. Call GetTestList with that tabIdentifier. This works and returns test identifiers like: ChatKitManagerCreationTests/testInitializesWithDependencies() Call RunSomeTests with tests = [{ targetName, testIdentifier }, …] (or call RunAllTests). Actual result The tool call fails with an MCP schema validation error like: Structured content does not match the tool's output schema: data/results/0 must have required property 'errors', data/results/1 must have required property 'errors', ... Why this looks like an xcode-tools bug According to the tool descriptor JSON for RunSomeTests / RunAllTests, each element of results[] is required to contain: targetName identifier displayName state errors (required, array of strings) But the actual response returned by RunSomeTests / RunAllTests appears to omit the errors field for one or more results (for passed tests it should still be present as an empty array []). Expected result RunSomeTests / RunAllTests always return structured content matching their declared output schema. In particular, every results[i] should include errors: [] when there are no errors. Environment Xcode: 26.3 macOS: Darwin 25.4.0 Workspace: Grocery.xcworkspace Scheme: GroceryCoreTests Active test plan: GroceryCoreTests Question Is this a known issue in Xcode 26.3’s MCP xcode-tools? Is there a workaround (e.g. alternative output mode, or reading a full summary file) until the schema/response is fixed?

Pulling my hair out here. After upgrading to Xcode Version 26.4.1 (17E202) I've started getting "unable to create tasks to copy stub binary: can't determine architectures of binary: /Applications/Xcode.app/Contents/Developer/Platforms/WatchSimulator.platform/Library/Application Support/MessagesApplicationStub/MessagesApplicationStub: Cannot open file handle for file at path: /Applications/Xcode.app/Contents/Developer/Platforms/WatchSimulator.platform/Library/Application Support/MessagesApplicationStub/MessagesApplicationStub: The file “MessagesApplicationStub” doesn’t exist." No matter what I do when trying to run the build (worked in previous versions). I've tried fresh install from App Store, direct package download, removing the SDKs, even previous versions and no matter what I get

Translated Report (Full Report Below) Process: Xcode [3078] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 26.4.1 (24909.0.3) Build Info: IDEApplication-24909000003000000~2 (17E202) Code Type: ARM-64 (Native) Role: Default Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [1424] User ID: 501 Date/Time: 2026-04-24 17:26:21.8348 +0800 Launch Time: 2026-04-24 17:26:21.7161 +0800 Hardware Model: MacBookPro18,1 OS Version: macOS 26.5 (25F5058e) Release Type: User Crash Reporter Key: 7A149229-7AEE-0654-7878-1A66190C590A Incident Identifier: AC932530-5FCF-45B1-90F3-D26B40150344 Time Awake Since Boot: 3400 seconds System Integrity Protection: enabled Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Exception Subtype: UNKNOWN_0x32 at 0x0000000112948000 Exception Codes: 0x0000000000000032, 0x0000000112948000 Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page

Hello everyone. I need help! I'm using Xcode solely to create an archive of a mobile application created with WinDev Mobile. When everything is working correctly, I simply retrieve the application's generated version from WinDev Mobile, launch the archive creation process, and add a new version to TestFlight! Then I can test the application on the iPhone. The current problem is that the application crashes, without any error message, in a specific use case. Hoping to get some help with this crash, I had the idea to test the application using Xcode. Once launched, a crash occurs if I follow the same process. There's an error message, which I'll paste below. What does this error mean? How can I relate it to my WinDev Mobile code? Have a good day.

Dear all, I am not able to transfer a programm to my iPhone 17, i get a certificate issue. Although i followed the general steps. If I was guided to this forum by the german apple support. Before in macOS Sonoma, with iOS 16 and iPhone 8 i have been able building programs for the iPhone. The Simulator has still no issues and works fine. Problem/Error: Certificate installation failed Installing a certificate in the keychain failed (Error Domain=DVTSecErrorDomain Code=-25295 "The specified keychain is not a valid keychain file." UserInfo={NSLocalisedDescription=The specified keychain is not a valid keychain file.}) No profiles for '-.delme2' were found Xcode couldn't find any iOS App Development provisioning profiles matching '-.delme2'. Furthermore, when I try to download a certificate myself via (https://developer.apple.com/account/resources/) I get the error: Unable to find a team with the given Team ID 'XXXXXXXCENSORED' to which you belong. Please contact Apple Developer Program Support. https://developer.apple.com/support In XCode I continue to receive the following information: So no programs can be transferred to my mobile phone. Objective: How do I get the reported errors resolved to transfer programs to my mobile phone?

I switch between Project / Tests / Breakpoints using top left pane 100s times a day. I also switch to search using CMD-Shift-F. In Xcode 26.4 I have to tap the <> to open menu. Is there a way to bring back the old behavior. Does any of the UX guys who worked on that feature use Xcode on daily basis? This is so bad :(

For the last 2 days, the claude agent has stopped working, it's not the issue where you get logged out after 8 hours, I have signed out and back in multiple times, quit xcode, nothing is working, every request just generates the following response: "Your request couldn't be completed."

My Family Controls (Distribution) capability request (C4N7962252) was approved March 15, 2026 for bundle ID com.jedsiegel.unplugtogether. All three Family Controls capabilities are enabled on the App ID. When I generate a provisioning profile (manual or automatic), Xcode reports: "Provisioning profile doesn't match the entitlements file's value for the com.apple.developer.family-controls entitlement." I decoded the profile using security cms -D and found: com.apple.developer.family-controls.app-and-website-usage → present com.apple.developer.family-controls → missing entirely My entitlements file requires com.apple.developer.family-controls with value ["individual"] for AuthorizationCenter. I've tried toggling capabilities off/on, deleting and recreating profiles, switching between automatic and manual signing, and clearing provisioning profile caches. Nothing works because the profile generation itself is not including the entitlement. Team ID: Q4RA4WMD6K Xcode 26.3, targeting iOS 26.2 Has anyone encountered this? Is there a way to get the provisioning system to include this entitlement?

Hi, We're experiencing inconsistent and unexpected values returned by Storefront.current?.countryCode when running our app via TestFlight. In our case: The device region and locale are set to Poland The App Store account (Media & Purchases) is also set to Poland However, when running a TestFlight build, Storefront.current?.countryCode sometimes returns a completely different value (e.g. "NO" for Norway), which does not match the current App Store account configuration. Here's the code we're using: if #available(iOS 15.0, *) { let code = await Storefront.current?.countryCode print("Storefront countryCode:", code ?? "nil") } What's particularly confusing: Across different devices logged into the same App Store account, we sometimes receive different countryCode values The returned value does not seem to reflect the current App Store region or device settings We understand that Storefront reflects the App Store storefront and not the device locale, but in this case the value appears stale or incorrect even with a properly configured App Store account. Questions: Is Storefront.current?.countryCode expected to behave differently in TestFlight vs. production builds? Are there known caching or propagation delays for storefront updates across devices? Can TestFlight builds return outdated or inconsistent storefront values? What is the recommended way to reliably determine the user's App Store region in this scenario? We rely on storefront to determine regional availability of features, so understanding this behavior is important for us. Thanks in advance for any clarification!

FB19249805 Main: The option to open files in New Window Tab doesn't appear anywhere in either Preferences or the contextual menu on clicking the files in the project (unlike previous Xcode versions). Only the option to open in New Tab is available (which is useless). This BREAKS EXISTING WORKFLOWS that have been established through years for countless developers. I can only see the option to open in New Tab, which breaks all existing workflows and habits. This results in an astonishing blow to productivity. Dear Xcode team: Please restore this option immediately! Additional details: Several years ago (I've been using Xcode since version 2), Xcode renamed the normal tabs into "Window Tabs" and introduced new "Tabs". The new "Tabs" proved to be a useless and counterproductive option for the following reasons: -They cannot be used in Behaviors. (Only Window Tabs can be, and many workflows have been built around this.) -It takes much longer to load a file into a Tab than into a Window Tab (where files are loaded nearly instantly). -Navigators and Inspectors cannot be customized for individual Tabs (only for Window Tabs). -Using both Tabs and Window Tabs is not an option, as it adds another tab bar that eats an enormous part of screen real estate without providing any benefits. Fortunately, we didn't have to use Tabs and could just disable them into oblivion where they belong. Now, in Xcode 26, the option to open files in new Window Tabs is gone. Really, I can only classify it as intentional sabotage. Many years of my Xcode habits and workflows are based on opening files in New Window Tabs via the Preferences > Navigation > With Option option. Or via the contextual menu. Now this option is gone. I'm sure there are plenty of other developers in the same situation. Please reenable the option to open in New Window Tabs. Thank you for your attention to this matter!

FB22576466 Another update - another blow to developers' productivity from the Xcode team, and more time wasted. Xcode 26.4.1 reset all windows and tabs in all projects. All carefully set up window tabs in multiple projects, as well as the ones that were previously open, are gone. Developers now have to set them up manually again. Ok there's nothing that can be done in 26.4.1 already; the damage has already been done. But dear Xcode development team... just DON'T. DO. THIS. AGAIN. Please! Tanks.

Previews seemed to be working okay. However, I wanted to test out some changes inside of a package that I'm working on for work, but in a lighter project since in our main project (where I have the package pulled in locally for now) is just too big to have the previews render in a decent amount of time. So, I opened a small project that was already importing that package and was set to 'Up to Next Major', but I switched that to 'branch' and added my branch. This is the second time I've done that and it causes Xcode to freak out in terms of the previews. This is the code I have: import SwiftUI extension EnvironmentValues { @Entry var trailingDescriptionColorToken: Color = .secondary } extension View { func updateTrailingDescriptionColor(to colorToken: Color, when trigger: Bool) -> some View { environment(\.trailingDescriptionColorToken, trigger ? colorToken : .secondary) } } // MARK: - ListItemDescription public struct ListItemDescription: View { @Environment(\.trailingDescriptionColorToken) var trailingDescriptionColorToken let description: String init(_ description: String) { self.description = description } public var body: some View { Text(description) .font(.caption) .foregroundStyle(trailingDescriptionColorToken) } } struct ContentView: View { @State private var isError = false var body: some View { VStack { Button("Error Trigger") { isError.toggle() } ListItemDescription("Description") .updateTrailingDescriptionColor(to: .red, when: isError) } .padding() } } #Preview { ContentView() } As soon as I tap the button to toggle the isError state property, that causes the preview canvas to indefinitely load and spin eventually leading to a crash. This is infuriating as I've just wasted a ton of time at work trying to figure out what's going on. Xcode and SPM is so fragile and delicate that at this point I feel like if I breathe on it wrong it'll break. I'm not sure what fixed it last time. Nothing in Xcode makes sense anymore. How to I resolve this please?

Hi everyone, yesterday i installed some package in my ios app , but i had a lot of problems to compile , due to reset my branch and get started from 0. My project have pods with firebase, lottie, instana and truskit but now, when a i try to run my project, xcode show "Unable to resolve module dependency" into LOTTIE, INSTANA, TRUSKIT, FIREBASE . I visited a lot of forums and websites, and i tried the followings steps: Pod deintegrate pod repoupdate pod install Clean build folder Delete derived data but isnot working. Also,I reinstalled xcode , 2 versions , i "re"clone my repository and the issue persist. Sorry, my english is basic only

I already have a working iOS React Native app and I’m planning to add a watchOS companion app. Is it possible to keep the iOS app and the watchOS app in separate repositories? If so, will WatchConnectivity still work properly between them? Or is it recommended to keep both in a single Xcode project/repository?

Has anyone got Xcode working with Opus 4.7? I have Claude Code running 4.7, but Xcode insists on running 4.6. Even working with Claude to try to configure Xcode doesn't work. Apparently Xcode does something that prevents using Opus 4.7. Any reason for this? Xcode has a really nice integration, but I guess It's bak to Terminal and Claude Code if I want to use the better Model. Anyone else got this working?

I am trying to create a test case in XCTest using the UI Test target. I have a use case where I use a SwiftUI Canvas to draw a network graph; and the user can drag the graph on the Canvas. After the drag, the user may click on a node. The application presents a popup with the information about the network node clicked. SwiftUI provides the information required for the application to translate the location of the tap into the original location prior to the drag; and so the logic behind the popup can determine which node the network graph was tapped by the user. It appears that the distance of the drag operation performed does not match distance that the image actually moved. The drag distance is always larger than the actual distance dragged. I can observe this during the test execution. The arrow starts at the correct spot but then goes further than the object being dragged. I also observe this when I am driving the application. Is there some standard and supported way to determine the distance that the image on the screen was moved given a specific distance of the "thenDragTo:" coordinate?

Hello together. Since a few weeks I have the problem, that both of my iPhones (iPhone 15 with iOS 26.4.1 and an iPhone Xs with iOS 18.7.4) are NOT recognized by xcode, but are visible in Mac Finder this is what xcode shows: When I click on that I see this: and in finder: I tried everyhting I re-installed XCode 5 times and deleted ALL XCode folders manually I restarted all devices and today I completely reinstalled my mac My Macbook has iOS 26.4.1 as well and XCode is freshly installed from App Store

Getting macOS app icons from Icon Composer working in Xcode 26.x appears to have caused widespread confusion. I've certainly had more than one headache from it. Here's what works for me: Drag the .icon file from Icon Composer into the Xcode Project Navigator, dropping it at the same level as Assets.xcassets — not inside it. In the Project Navigator, click the top-level project item to open the Project Editor. Select your app target and open the App Icons and Launch Screen section. Enter the icon name (without the .icon extension) in the App Icon field. In that same section, leave App Icons Source unchecked. Go to the Build Phases tab and expand Copy Bundle Resources. Delete the Assets.xcassets entry, leaving only the .icon file. Clean the build folder (⇧⌘K) and run. Your icon should now appear in the Dock. It appears that Icon Composer icons and even the presence of the Asset Catalog icons in Copy Bundle Resources are mutually exclusive right now. Including the Asset Catalog appears to suppress the Icon Composer icon. Removing it lets the Icon Composer icon through. Note: If your app depends on other assets in the Asset Catalog, this approach won't work for you. In that case, fall back to the traditional method — export all required sizes from Icon Composer and import them into the Asset Catalog. Hopefully Apple addresses this conflict soon.

Whenever I try and talk to chatgpt codex in Xcode, I get the request could not be completed error with this tag: JSON-RPC global stream failed: The operation couldn’t be completed. (IDEIntelligenceAgents.JSONRPCElement.Error error 1.) Chatgpt chat still works inside of xcode, however codex does not work. I have not hit my limit for codex. This issue happened after the xcode update. (I belive 26.4.1)

Took app and selected Archive. Selected Direct Distribution. Process completed. I selected export app. Could not elect the app to export since it was greyed out. Queried on both google and Claudie. Followed all the instructions and there is still no joy. Worked fine yesterday.