I'm based in Australia, and am having the following issue. After leaving this message I received another response from someone else who is also havign the same issue, I've pasted that too. I'm quite surprised to not see it mentioned, could be local to language settings or something. Here is the issue: Folk, I am having an issue where Xcode 26.3 with the new iOS26.2+26.3.1 Simulator update installed doesn’t render Unicode characters in the Canvas or in Simulator. They do render when running direct to a device. I’ve reset devices inside Simulator, cleared Derived Data, cleaned Build Folders etc but to no avail! Is anyone else seeing this, I can’t find a mention anywhere!! Thank you in advance. Yep. Same here. Can't see emojis on the emoji picker keyboard.

Was working before, no longer working this week. Trying to sign in to my Claude Pro account via Xcode Intelligence. Goes to browser, I login, and accept authorization in Claude then redirect back to Xcode is reject. Everytime, multiple browsers, and even trying the add "/" that others have noted for other cases.

after upgrade macos version to 15.4 the rsync start failing that cause the xcodebuild fail and not generate ipa rsync: on remote machine: --extended-attributes: unknown option rsync error: syntax or usage error (code 1) at main.c(1802) [server=3.4.1] rsync(73444): error: unexpected end of file rsync(73444): error: io_read_nonblocking rsync(73444): error: io_read_buf rsync(73444): error: io_read_int rsync(73444): warning: child 73445 exited with status 1

Every time I touch (add a key, remove a key, even add a key, then remove it) the Strings Catalog .xcstrings file, it re-renders the entire file and creates a 18 thousand line dif. When I looked closer, it changes the whitespace before colons! "version": "1.0" "version" : "1.0" it does so for every JSON node. This makes the whole feature useless, because we wont be able to see what we changed upon code review (diff is unprintable in the github interface) and every time we change a single translation, we will be stacking 18k lines diff. Not to mention merge conflicts?

Hi everyone, I'm working in a strictly offline (intranet) environment and cannot use the standard online installation process to download and install the Claude Agent for Xcode. What I've tried: I manually copied the Agent binary/folder from an online machine to the following path: ~/Library/Developer/Xcode/CodingAssistant/Agents/Versions/26.3/claude The Issue: Even though the files are in the correct directory, Xcode fails to recognize the agent. It doesn't appear in the settings, and the Coding Assistant remains unavailable. Questions: Is there a specific metadata file (e.g., a .plist or .json index) that needs to be updated for Xcode to "see" the manually added agent? Are there any code signing or quarantine issues (like xattr) that need to be addressed when moving the agent between machines? Does anyone know if there are other dependencies or cache folders (besides ~/Library/Developer/Xcode/CodingAssistant/) that need to be synchronized? Environment: macOS: 26.3 (25D122) Xcode: 26.3 (17C519) Any guidance on the manual registration process for these agents would be greatly appreciated. Thanks!

0 0x1001bd52c __assert_rtn + 252 1 0x100132054 void std::__1::__introsort<std::__1::_ClassicAlgPolicy, ld::AliasAddressOrderer&, ld::Atom const**, false>(ld::Atom const**, ld::Atom const**, ld::AliasAddressOrderer&, std::__1::iterator_traits<ld::Atom const**>::difference_type, bool) + 0 2 0x1001319a4 ld::LayoutLinkedImage::assignAtomOffsetsInSection(ld::SectionLayout&, unsigned int, bool) + 680 3 0x100136724 void dispatchForEach<ld::SectionLayout*, ld::LayoutLinkedImage::sortAtomsWithinSections()::$_0>(std::__1::span<ld::SectionLayout*, 18446744073709551615ul>, unsigned long, ld::LayoutLinkedImage::sortAtomsWithinSections()::$_0)::'lambda'(unsigned long)::operator()(unsigned long) const + 7852 4 0x19dca8aec _dispatch_client_callout2 + 16 5 0x19dca37f8 _dispatch_apply_invoke3 + 336 6 0x19dca8ad4 _dispatch_client_callout + 16 7 0x19dc91a60 _dispatch_once_callout + 32 8 0x19dca2938 _dispatch_apply_invoke + 252 9 0x19dca8ad4 _dispatch_client_callout + 16 10 0x19dcc59dc _dispatch_channel_invoke.cold.5 + 32 11 0x19dca113c _dispatch_root_queue_drain + 736 12 0x19dca1784 _dispatch_worker_thread2 + 180 13 0x19de47e10 _pthread_wqthread + 232 ld snapshot written at /tmp/****app.debug.dylib-2026-03-24-092748.ld-snapshot ld: Assertion failed: (aliasSectionNum == sectionNum && "alias and its target must be located in the same section"), function assignAliasAtomOffsetInSection, file Layout.cpp, line 4805. clang: error: linker command failed with exit code 1 (use -v to see invocation) I want to submit an ld-snapshot attachment, but the "Add File" function in the posting section won't let me add any files. My macOS was upgraded from version 16 to 26.3, and my Xcode was upgraded from version 16.1 to 26.3. Please help me resolve this as soon as possible, thank you.

Help please! I'm new to Xcode and my Mac is a 2021 MacBook Pro. I've downloaded Xcode recently (version 26.2) and wanted to preview and test my first App. But somehow, I just can't download the iOS simulator. People tell me that I can download resources from developer.apple.com, but I only found the iOS_18.2_runtime.dmg. I downloaded and installed the iOS 18.2 version but Xcode still requires to download the iOS 26.2 simulator. I don't know why and how to fix this problem. Please help!

I’m working on an iOS workspace with: a static library project: M800SDK a test app project: TestAppObj I was able to build M800SDK for iOS Simulator on Apple Silicon as a simulator static library, and I also verified the architectures in the produced .a file. However, when I link the app target against that simulator build and try to build TestAppObj for iOS Simulator, I get the following linker errors: Undefined symbols for architecture arm64: _OBJC_CLASS_$_TokenMngr clang++: error: linker command failed with exit code 1 Additional context: The library links and works correctly when building the app for a physical iPhone. And the public header TokenMngr.h is found correctly by the app target. The app target is compiled as Objective-C++ where needed. The library is linked in the app target under “Link Binary With Libraries”. Could you help me understand: Is it possible to run on iOS Simulator ? the recommended way to package and consume this library for iOS Simulator on Apple Silicon? Also I am aware i can also build the library for : Any iOS Simulator Device (arm64, x86_64) And specify that on Build Phases in Link : Link Binary With Libraries adding the .a Before i do that i ensure the .a is arm64, x86_64 using the command : lipo -info libM800SDK.a end it returns : Architectures in the fat file: libM800SDK.a are: x86_64 arm64 However, even after confirming those architectures and linking the library to the app target, the app still does not link correctly for iOS Simulator. In some cases, Xcode reports errors suggesting that the build is targeting iOS Simulator, but that one of the linked binaries was built for iPhoneOS instead. This is where I am confused: I understand that lipo -info only shows the CPU architectures present in the library, but not whether a given arm64 slice was built for iPhoneOS or for iOS Simulator

[Reply to DTS Engineer] Thank you for looking into this. I have identified the root cause of the issue: it is a Bundle ID case-sensitivity mismatch. My parent app was approved as com.hayashikento.FocusPact (Capitalized), but I accidentally requested the Configuration Extension with a lowercase ID (com.hayashikento.focuspact...). This causes a "Prefix Mismatch" error in Xcode, preventing me from archiving the app. To fix this, I have just submitted a new entitlement request with the corrected capitalized ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Since the core functionality was already approved under the lowercase ID, could you please expedite the approval for this capitalized version? This technical correction is the only thing blocking my TestFlight distribution. Thank you for your support!

Setup: Xcode 26.3. MacOS Tahoe 26.3.1 Signed in for Coding Intelligence with Claude Pro plan. For the first 3 prompts Claude responded normally. Afterwards it always responds with "Your request couldn't be completed."

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.