I'm trying to use Xcode 26.3's official MCP Server (xcrun mcpbridge) on an Intel Mac（15.7.4）, but it crashes immediately. Run xcrun mcpbridge in Terminal： dyld[3809]: Symbol not found: _$s10AppSandbox17ASBBinaryIdentityC14teamIdentifierSSSgvg Referenced from: /Applications/Xcode.app/Contents/Developer/usr/bin/mcpbridge Expected in: /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox [1] 3809 abort xcrun mcpbridge Observations The same command works on an Apple Silicon Mac (M1, macOS 26.3).

Hi Guys, Hope you're well! I am consistently encountering a build warning in Xcode 26 that prevents proper symbolication of crash logs. The warning states: "warning: (arm64) /Users/mickey/Library/Developer/Xcode/DerivedData/CalendarSync-bjuvwxojzofqzzcmzzpdozbujrge/Build/Products/Debug-iphoneos/CalendarSync.app/CalendarSync empty dSYM file detected, dSYM was created with an executable with no debug info." Steps to Reproduce: Open the project in Xcode 26. Build the project for a physical iOS device (arm64) or Archive the project. The warning appears during the "Generate dSYM" phase of the build process. Troubleshooting Steps Already Taken (Issue Persists): Set 'Enable Debug Dylib Support' to No. Verified 'Debug Information Format' is set to 'DWARF with dSYM File'. Verified 'Generate Debug Symbols' is set to Yes. Set 'Strip Debug Symbols During Copy' and 'Strip Linked Product' to No. Performed 'Clean Build Folder' and manually deleted the DerivedData folder. The issue persists regardless of these standard configuration fixes. Expected Result: Xcode should generate a populated dSYM file containing the debug symbols from the executable. Actual Result: An empty dSYM file is generated, making it impossible to symbolicate crash reports.

Hello, I have a critical issue regarding the "Family Controls (Distribution)" entitlement. My app "FocusPact" was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a "Bundle identifier prefix mismatch" error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an already authorized functionality. Team ID: UHG4J7F7NH App Apple ID: 67591326449 Thank you for your assistance. I am a student developer eager to start MVP testing as soon as this is resolved.

This just started happening today out of nowhere. Instead of only the project I’m working on appearing in Source Control, every project inside my Xcode projects folder is now showing up in the Source Control navigator. This is happening in both the Changes and Repositories tabs.

Im a Quality Engineer and using Appium to automate in Physical devices so installed appium server and xcuitest. We need to build the webdriveragent project from xcode , when doing that getting the following error "Your team has no devices from which to generate a provisioning profile. Connect a device to use or manually add device IDs in Certificates, Identifiers & Profiles. https://developer.apple.com/account/" I have a apple account licensed but still unable to resolve this, any immediate help is highly appreciated

I have the following setup: UIViewRepresentable with a UIView holding UIScrollView ImageView PKCanvasView this is in order to make it appear as if you are writing on a paper which you can zoom and scroll. The UIImageView is holding the paper image. The problem is if you draw some pen strokes at zoom level 1, then zoom in (say zoom level 2) as soon as you place down the pen, the PKCanvasView starts flickering repeatedly very badly. A sample video is here: https://youtube.com/shorts/5zeq6EDheSM a small sample project showing this is here: https://www.icloud.com/iclouddrive/0a0NSLP4bsism69L7jRtZPIhQ#BugDemo

I have three rogue iOS simulators, how to correctly delete them and reclaim the disk space? These img files are costing me 18gb of storage.

I would like to have the option to keep my xcode project open regardless of closing all tabs using cmd + w.

I am trying to preview my SwiftUI views but Xcode Preview Canvas failing. I tried everything that I found at internet but nothing works. Finally I created a new iOS project that contains only a view import SwiftUI struct ContentView: View { var body: some View { VStack { Image(systemName: "globe") .imageScale(.large) .foregroundStyle(.tint) Text("Hello, world!") } .padding() } } #Preview { ContentView() } Even this view cannot be previewed The error is Simulator was shutdown during an update Simulator [3E0DB935-C4C2-4566-BA48-8E21564C207C] failed to boot and may have crashed. I tried to restart xCode, restart Mac, download ios 26.0 sdk and created a simulator with that sdk but nothing helped. Do you have an idea?

I've got a Project with a bunch of frameworks, each of which has a static library version of itself (for compiling command-line tools that also use the code). Compiling the frameworks goes fine. Compiling one of the static libraries (A Mime-parsing framework) is giving me the rather odd message that a bunch of symbols are ambiguous, but the ambiguity resolves to the same symbol in the error-message... ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:57:18: error: reference to 'E3_SMIME_ENVELOPED_DATA' is ambiguous 57 | case E3_SMIME_ENVELOPED_DATA: | ^ In file included from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:9: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:17:2: note: candidate found by name lookup is 'E3_SMIME_ENVELOPED_DATA' 17 | E3_SMIME_ENVELOPED_DATA, // Enveloped data | ^ In module 'E3Mime' imported from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:8: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:17:2: note: candidate found by name lookup is 'E3_SMIME_ENVELOPED_DATA' 17 | E3_SMIME_ENVELOPED_DATA, // Enveloped data | ^ ... and again ... ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:62:18: error: reference to 'E3_SMIME_SIGNED_DATA' is ambiguous 62 | case E3_SMIME_SIGNED_DATA: | ^ In file included from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.m:9: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:18:2: note: candidate found by name lookup is 'E3_SMIME_SIGNED_DATA' 18 | E3_SMIME_SIGNED_DATA, // Signed data | ^ In module 'E3Mime' imported from ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:8: ~/src/E3Mail/Frameworks/E3Mime/E3Mime/Message/MIME/E3AppPkcs7Part.h:18:2: note: candidate found by name lookup is 'E3_SMIME_SIGNED_DATA' 18 | E3_SMIME_SIGNED_DATA, // Signed data | ^ ... and again, etc ... . No file inside the module (neither .m or .h) includes the module-header, the definition of the offending symbols looks like: // // E3AppPkcs7Part.h // E3Mime // #import <E3Mime/E3CryptoContext.h> #import <E3Mime/E3MimePart.h> #import <E3Mime/E3MimeMultipartEncrypted.h> NS_ASSUME_NONNULL_BEGIN typedef enum { E3_SMIME_COMPRESSED_DATA, // Compressed data E3_SMIME_ENVELOPED_DATA, // Enveloped data E3_SMIME_SIGNED_DATA, // Signed data E3_SMIME_CERTS_ONLY, // Only certificate data E3_SMIME_UNKNOWN, // Que ? } E3SMimeType; ... And when I click on the error adornment in the editor pane, the errors disappear. It still won't build the project, though. I just get the same errors the next time I press CMD-B. Can't upload a short screen-capture of that, so I put it the movie at http://0x0000ff.co.uk/mov/phantom-errors.mov.

When working in parallel on 2 projects (i.e. a server and a client app project). The Claude Code agents in those projects should be able to communicate with each other to improve the flow of information (i.e. changes in models, DTOs). The developer should supervise the communication and can block, if necessary.

Xcode 16 and 26 changes in painful way how the Tab key works during autocomplete. Previously, pressing Tab would extend the typed text up to the word match. For example, we have two classes: NSViewController and NSViewCoordinator BEFORE, typing: "NSV" + Tab used to complete to NSViewCo Now, in Xcode 26, pressing Tab just use the first suggestion. Stupidly. Especially when you want DispatchQueue and it gaves you DispatchSemaphore… That is very inconvenient because very often I want just see all possible cases with some prefix...without need of typing all prefix manually. How to restore the previous behavior? How to do autocomplete word-by-word?

Hi, I am working on app at the moment that uses Icon Composer for all of its icons and variations. I want to add an iMessage App to my project however I get validation errors from App Store Connect even if I add an imessage app to my asset catalog and include all app icon assets. Is there any way to do this at the moment natively with Icon Composer? If not how do I manually overwrite the icon JUST for iMessage and not for my entire iOS app?

I work on an SDK, and one of the ways we distribute it is as a pre-compiled static XCFramework. As far as I know, it’s the nature of a static framework to not contain symbols since the framework will be embedded in the final app binary, and the symbols should then be generated. However, when testing the "Validate" function of the Xcode 16 deployment process, our users are receiving a warning that says the framework does not contain symbols. Is my assumption about static frameworks and symbols incorrect? Could this be a bug in Xcode 16? Should we modify something in our framework to inform Xcode that symbols are not needed?

For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives "Server SSH Fingerprint Failed to Verify" as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?

Have a peculiar problem I'm not able to solve. Working on an app with a mapview in the max zoomed out globe level. For some reason this morning Xcode froze/crashed when I was working and I had to force quit to get it back up. Then a new issue of graphical artifacts on the space section of the Mapview showed up. This Tuesday has now been spent in full on trying to solve this to no avail. I created a new project for iOS/iPadOS and added a similar map implementation. It works fine. I used Claude to help me after a few reinstalls of Xcode with this. I asked claude to summarize - this is what has been done: Claude generative AI summary starts here---------- Here's a complete summary of everything attempted: The Problem SwiftUI tvOS app with MapKit globe view showing severe rendering artifacts — corrupted pixels surrounding the globe. Started after Xcode crashed while the tvOS simulator was actively running. iOS simulator, macOS Maps app, and all native apps work perfectly. Only tvOS simulator MapKit is affected. Hardware Confirmed Fine Geekbench 6 Metal GPU score: 124,666 (normal for M1 Max) Apple Diagnostics (Apple Silicon method): No issues found macOS Maps globe renders perfectly Everything That Was Attempted Simulator resets: Erased all simulator content and settings Created brand new simulator devices Deleted derived data Killed CoreSimulator service Runtime reinstalls: Removed and reinstalled tvOS platform runtime multiple times Tested on Xcode 26.3 and 26.4 beta — same issue on both Installed fresh tvOS runtime after full Xcode reinstall Cache clearing: ~/Library/Caches/com.apple.CoreSimulator ~/Library/Saved Application State/com.apple.iphonesimulator.savedState All Metal shader caches in /private/var/folders/ including: com.apple.CoreSimulator.SimRenderingServices.SimMetalHost com.apple.CoreSimulator.SimRenderingServices.SimRenderServer com.apple.CoreSimulator.CoreSimulatorService com.apple.iphonesimulator com.apple.dt.Xcode com.apple.dt.xcodebuild com.apple.CoreSimulator.simctl ~/Library/Developer/Xcode/XcodeToMetalToolchainIndexMapping.plist ~/Library/Developer/Xcode/SDKToSimulatorIndexMapping.plist ~/Library/Developer/Xcode/DerivedData Full Xcode reinstall: Deleted Xcode completely Removed ~/Library/Developer Removed all Xcode-related caches and preferences Fresh install from Mac App Store APFS simulator volume cleanup (required disabling SIP): Discovered 138GB of orphaned APFS simulator volumes in /Library/Developer/CoreSimulator/Volumes/ that were protected by SIP and couldn't be deleted normally These volumes were left in a corrupted/limbo state from the original Xcode crash Temporarily disabled SIP via Recovery Mode Successfully deleted all orphaned volumes Re-enabled SIP Reinstalled fresh tvOS runtime Metal Toolchain: Found three leftover Metal Toolchains (17A324, 17A5241c, 17A5295f) in Xcode settings Cleared toolchain index mapping file Reinstalled fresh Metal Toolchain with new tvOS runtime Current State Fresh Xcode installation Fresh tvOS runtime All simulator volumes cleared SIP re-enabled Issue still persists What Has NOT Been Checked /Library/Developer/CoreSimulator/Cryptex /Library/Developer/CoreSimulator/Images /Library/Developer/CoreSimulator/Profiles Conclusion This is almost certainly a bug triggered by the hard Xcode crash corrupting something at a level that has survived complete reinstallation of Xcode and all simulator components. The corruption is somewhere in a system-level component that normal developer tools cannot reach. Requires Apple Developer Technical Support or escalation via Feedback Assistant with the full timeline and screenshots. For Apple's reference: Machine: MacBook Pro M1 Max Xcode: 26.3 / 26.4 beta (both affected) Started: After hard Xcode crash while tvOS simulator was actively rendering MapKit globe Affected: tvOS simulator MapKit globe only Not affected: iOS simulator, macOS Maps, all native apps ----------(Claude generative AI summary ends here) ----------- Anyone seen this before? Absolutely wild. Can't think of more things to try. Been eyeing a new Macbook for a while. Strange coincidence that the new M5 Macbook Pros dropped today :D But in sum it does not seem like a GPU issue since the same rendering works on the iOS sim. Thanks!

Can I download the iOS 26 simulator runtime via a download link? The machine I need to deploy on may require an offline package installation due to firewall restrictions.

In the Coding Intelligence feature introduced in Xcode 26, when I send a message using ChatGPT in Xcode, the message “Your request couldn't be completed. Networking error.” appears and I’m unable to use the feature. I suspect the issue may be related to the VPN or network proxy connected to my Mac and am attempting to investigate. However, Xcode does not display any specific error details, nor does it provide a way to view them, which makes a detailed investigation difficult. Next to the error message, there is a feedback button rather than a stethoscope (🩺) button, and the feedback window does not provide access to the underlying error information. Is there a way to view the detailed network error logs generated by ChatGPT in Xcode? (I am using Xcode 26.0.1.)

Can I download the iOS 26 simulator runtime via a download link? The machine I need to deploy on may require an offline package installation due to firewall restrictions.

I'm following the steps laid out in Creating a static framework which states: When a client links and embeds the framework, Xcode 15 or later omits the main binary from the embedded framework bundle because it’s already statically linked into the client. Specifically, I'm adding a new framework target to my project, and then changing the Mach-O type in its build settings to Static Library. What I'm observing when I build (debug or release) is that that the resulting framework folder inside of the app bundle still contains a binary. Furthermore, upon inspecting strings and symbols in both the main app executable and this library binary, it appears that my strings and symbols do end up in the main executable and not in the library binary. Does this mean that this binary is just a stub left behind? Is this intended? Can I safely delete this binary with a build phase script?