I have been trying for 24 hours to upload app, and first time this has happened in 8 years and 100+ uploads. Please help. Validate App and Upload both hang indefinitely at "Preparing" in Xcode Organizer. No error is ever returned — the progress bar freezes and the operation never completes or times out. Transporter 1.4.5 fails identically. Key detail: archive 2.4.3 (build 123), which Apple accepted and processed on Sept 10, 2026, now hangs the same way when validated. Same machine, same Xcode, same Apple ID. This rules out the archive, its signature, and its provisioning profile. Already ruled out: two independent networks (home Wi-Fi and iPhone cellular hotspot); the archive itself (known-good build 123 fails identically); Xcode install (27.0 / 27A266a, xcode-select verified correct); Apple ID session (signed out and back in three times); full reboot. macOS 27.0 (26A428) on MacBookPro18,4. Last successful upload Sept 10, 2026. 100+ prior archives uploaded without incident over several years. macOS has updated twice since Sept 10. Separately: Transporter 1.4.5 crashes on macOS 27.0 with an unhandled exception in TransporterKit while drawing its activity queue (EXC_BREAKPOINT via +[NSApplication _crashOnException:]).

Hello all, Yesterday, I found out that there's 60GB's of old simulator volumes on my mac in /Library/Developer/CoreSimulator/Volumes/. When I try to delete those through Xcode Settings -> Components under Other Installed Platforms, it looks like they are deleted, but after restarting my Mac, they simply return. I tried the solution proposed here (which is to delete the dmg files in /Library/Developer/CoreSimulator/Images/), but in my case, there are no dmg files in there. So it looks like they were properly deleted, unlike those in /Library/Developer/CoreSimulator/Volumes/. I could obviously try to delete the dmg files in /Library/Developer/CoreSimulator/Volumes/, but that doesn't work according to a post on reddit that I'm not allowed to show here (It's called 'Deleted 240GB of Xcode simulators multiple times but they keep remounting - how do I permanently remove them?') And I wonder if it's a safe thing to do. Do you have any suggestions for how to remove the old volumes correctly and permanently?

It looks like the other thread got locked. I would still like to be able to uncheck the box for "Connect via network" so I can develop with my iOS 17+ devices normally with Xcode 15. Or a method to use Xcode 14 with iOS 17+ without CoreDevice or whatever the problematic API is.

Environment: Xcode 27 (macOS 27.0, build 26A428) iOS 27.0 simulator (build 24A434), tested on iPhone 18 Pro CoreSimulator 1174.9.2 Large app target: dozens of linked frameworks (first-party SPM modules plus several third-party SDKs) it occurred on xcode 26 also Description: SwiftUI canvas previews consistently crash XCPreviewAgent with EXC_BAD_ACCESS / SIGSEGV when rendering previews for a fairly large app target, across multiple different SwiftUI views (not tied to one specific file's code). Workaround found: the crash does not occur when "Use Legacy Preview Execution" is enabled (Xcode's preview settings). With the default (non-legacy, JIT-based) preview execution path, it crashes reliably; switching to legacy execution, previews render normally. Possible contributing factor — project size / timing: we suspect the size of the project may also be a factor, independent of the crash itself. The new (non-legacy) execution path recompiles/JITs the app for the canvas on every preview, and for a target this large that process takes noticeably longer than it does under legacy execution. It's plausible that on top of the crash described below, the new path is also more prone to timing out or failing under load on larger projects, simply because there's more to JIT-compile and load within whatever time budget the preview agent allows. We can't fully separate "crashes because of X" from "runs out of time because of project size" from the crash logs alone, but both seem worth flagging since they may share the same root cause in the new execution path's handling of larger binaries. Crash signature #1 (default preview execution, first attempts): Crashing Thread: 0 libswiftCore.dylib swift_conformsToProtocolMaybeInstantiateSuperclasses(...) 1 libswiftCore.dylib swift_conformsToProtocolWithExecutionContext 2 libswiftCore.dylib swift::_conformsToProtocol(...) 3 libswiftCore.dylib swift::_checkGenericRequirements(...) Termination: SIGSEGV / Segmentation fault: 11 Crash signature #2 (default preview execution, after removing an unrelated third-party SDK dependency from the previewed module, to rule it out as a cause): Crashing Thread ("com.apple.xojit_executor.wrapper_functions"): 0 libobjc.A.dylib readClass(objc_class*, bool, bool) 1 libobjc.A.dylib map_images_nolock 2 libobjc.A.dylib map_images 3 libobjc.A.dylib _objc_map_images 4-7 <unsymbolicated / anonymous image, source="A" (Absent) in the crash report> Exception: EXC_BAD_ACCESS (SIGSEGV), KERN_INVALID_ADDRESS In the second case, the crash log's usedImages list shows the frames above the objc runtime resolving to an image with no path, no resolvable UUID, and "source": "A" — this appears to be the dynamically JIT-compiled preview binary that XOJITExecutor builds and hot-loads for the canvas (rather than a normal on-disk framework), and the crash occurs while the Objective-C runtime is registering classes from it during _objc_map_images. What we've ruled out: Not caused by the specific SwiftUI view being previewed — reproduces across multiple unrelated views in the same target. Not caused by a specific third-party SDK: we removed a heavyweight closed-source analytics SDK dependency from the previewed module entirely (confirmed via successful xcodebuild build with zero references left), and the crash still occurred with an equivalent signature under default preview execution. Confirmed via symbolicated .ips crash reports in ~/Library/Logs/DiagnosticReports/XCPreviewAgent-*.ips that the crashing frames are inside Apple's own preview infrastructure (libobjc.A.dylib, libswiftCore.dylib, XOJITExecutor), not in application or third-party framework code. Confirmed the failure is specific to the new (non-legacy) preview execution path: enabling "Use Legacy Preview Execution" eliminates the crash entirely, with no other changes. Question for the community: Has anyone else seen SwiftUI Previews crash with a libobjc/map_images or swift_conformsToProtocol* segfault specifically on Xcode 27 / iOS 27 simulator with the new (non-legacy) preview execution path, for apps with a large number of linked frameworks? Does project size/build time make the new execution path more likely to fail or time out for anyone else? Is "Use Legacy Preview Execution" the recommended workaround until this is fixed, or should this be filed separately as Feedback?

For the life of me, I cannot find how to bring up the Siri Remote in the Apple TV Simulator in Xcode 27 Device Hub (Beta). Is it no longer available? I have always seem to have had issues using the computer's keyboard for navigating my tvOS apps. Maybe it's me, but the Siri Remote always worked perfectly fine. I hope the remote will make a reappearance in the next beta... ?

Is anyone else having issues uploading an archive to App Store Connect? I went to validate an archive of my app, and seems to hang during validation. I've tried just validating the app, and tried Transporter as well. It hangs on the analyzing app. How to troubleshoot?

Xcode 27 keeps failing to download the Documentation, it shows "Preparing to download" and spins the camomile endlessly. I checked logs (with help of AI) and found this: Xcode queries com.apple.MobileAsset.AppleDeveloperDocumentation. Metadata catalog loading suceeds. Then asset resolution loops with: MAQueryTooManyResults - Asset load result ... 13 (MAQueryTooManyResults) Also CSSMERR_CSP_VERIFY_FAILED from mobileassetd during this sequence. In my /System/Library/AssetsV2 I have 3 old .asset files all from Xcode 26, the last one updated on Jun 12. But I don't think it's the reason for the error. What would you suggest to recover the documentation?

Hello, I noticed that iPhone 18 series devices are missing from DeveloperDiskImages in Xcode 27.1 beta 1. I checked /Library/Developer/DeveloperDiskImages/iOS_DDI/Restore/BuildManifest.plist and found no entries for iPhone 19,x in SupportedProductTypes. Could this be due to downloading the wrong version of Xcode, or is there another reason? Latest iPhone type is iPhone18,5, here is the content of BuildManifest.plist from Xcode 27.1 beta 1: <key>ManifestVersion</key> <integer>0</integer> <key>ProductBuildVersion</key> <string>27A9269</string> <key>ProductVersion</key> <string>1.0</string> <key>SupportedProductTypes</key> <array> <string>ComputeModule13,1</string> <string>ComputeModule13,3</string> <string>ComputeModule14,2</string> <string>Mac14,14</string> <string>iPad11,1</string> <string>iPad11,2</string> <string>iPad11,3</string> <string>iPad11,4</string> <string>iPad11,6</string> <string>iPad11,7</string> <string>iPad12,1</string> <string>iPad12,2</string> <string>iPad13,1</string> <string>iPad13,10</string> <string>iPad13,11</string> <string>iPad13,16</string> <string>iPad13,17</string> <string>iPad13,18</string> <string>iPad13,19</string> <string>iPad13,2</string> <string>iPad13,4</string> <string>iPad13,5</string> <string>iPad13,6</string> <string>iPad13,7</string> <string>iPad13,8</string> <string>iPad13,9</string> <string>iPad14,1</string> <string>iPad14,10</string> <string>iPad14,11</string> <string>iPad14,2</string> <string>iPad14,3</string> <string>iPad14,4</string> <string>iPad14,5</string> <string>iPad14,6</string> <string>iPad14,8</string> <string>iPad14,9</string> <string>iPad15,3</string> <string>iPad15,4</string> <string>iPad15,5</string> <string>iPad15,6</string> <string>iPad15,7</string> <string>iPad15,8</string> <string>iPad16,1</string> <string>iPad16,10</string> <string>iPad16,11</string> <string>iPad16,2</string> <string>iPad16,3</string> <string>iPad16,4</string> <string>iPad16,5</string> <string>iPad16,6</string> <string>iPad16,8</string> <string>iPad16,9</string> <string>iPad17,1</string> <string>iPad17,2</string> <string>iPad17,3</string> <string>iPad17,4</string> <string>iPad5,1</string> <string>iPad5,2</string> <string>iPad5,3</string> <string>iPad5,4</string> <string>iPad6,11</string> <string>iPad6,12</string> <string>iPad6,3</string> <string>iPad6,4</string> <string>iPad6,7</string> <string>iPad6,8</string> <string>iPad7,1</string> <string>iPad7,11</string> <string>iPad7,12</string> <string>iPad7,2</string> <string>iPad7,3</string> <string>iPad7,4</string> <string>iPad7,5</string> <string>iPad7,6</string> <string>iPad8,1</string> <string>iPad8,10</string> <string>iPad8,11</string> <string>iPad8,12</string> <string>iPad8,2</string> <string>iPad8,3</string> <string>iPad8,4</string> <string>iPad8,5</string> <string>iPad8,6</string> <string>iPad8,7</string> <string>iPad8,8</string> <string>iPad8,9</string> <string>iPhone10,1</string> <string>iPhone10,2</string> <string>iPhone10,3</string> <string>iPhone10,4</string> <string>iPhone10,5</string> <string>iPhone10,6</string> <string>iPhone11,2</string> <string>iPhone11,4</string> <string>iPhone11,6</string> <string>iPhone11,8</string> <string>iPhone12,1</string> <string>iPhone12,3</string> <string>iPhone12,5</string> <string>iPhone12,8</string> <string>iPhone13,1</string> <string>iPhone13,2</string> <string>iPhone13,3</string> <string>iPhone13,4</string> <string>iPhone14,2</string> <string>iPhone14,3</string> <string>iPhone14,4</string> <string>iPhone14,5</string> <string>iPhone14,6</string> <string>iPhone14,7</string> <string>iPhone14,8</string> <string>iPhone15,2</string> <string>iPhone15,3</string> <string>iPhone15,4</string> <string>iPhone15,5</string> <string>iPhone16,1</string> <string>iPhone16,2</string> <string>iPhone17,1</string> <string>iPhone17,2</string> <string>iPhone17,3</string> <string>iPhone17,4</string> <string>iPhone17,5</string> <string>iPhone18,1</string> <string>iPhone18,2</string> <string>iPhone18,3</string> <string>iPhone18,4</string> <string>iPhone18,5</string> <string>iPhone8,1</string> <string>iPhone8,2</string> <string>iPhone8,4</string> <string>iPhone9,1</string> <string>iPhone9,2</string> <string>iPhone9,3</string> <string>iPhone9,4</string> <string>iPod9,1</string> <string>iSim1,1</string> </array>

I am unable to debug an iOS 27 device using Xcode 26. I can not currently update Xcode so I'm stuck with it for the time being. There used to be the hack where you could copy the newer /Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport into the older Xcode, but that path doesn't exist in Xcode 27. Is there any way to debug an iOS 27 device using Xcode 26? Currently I see "Insufficient metadata to manage symbols" in Devices & Simulators for that connected device.

Hello, I’m trying to pair an Apple Watch Ultra 4 running watchOS 27 with Xcode 27, but the watch does not appear in Device Hub or under “Pair Nearby Device”. The iPhone paired with the watch is detected correctly by Xcode. Developer Mode is enabled on both devices, and the Mac, iPhone, and Apple Watch are on the same Wi-Fi network. I have already tried restarting all devices, connecting the iPhone by USB, disabling and re-enabling Bluetooth and Wi-Fi, disabling VPN/firewall software, and checking that the watchOS Developer Disk Image is installed and usable. The watch still does not appear as a physical device. Only Apple Watch simulators are listed. Has anyone experienced this issue or found a workaround? Thank you.

Dear Friends, Is there a way to increase font size of xcode intelligence window? So the text i write, and the AI response. Why do i need this? I am using 4K monitor and i dont want to make Display setting bigger and lose all screen space.

Hi everyone, I downloaded Xcode 27.0 today because I need the Metal Toolchain for Unreal Engine 5.6 on my Mac. Xcode itself is installed and working, but Unreal is having issues because the Metal Toolchain doesn't seem to be installed. When I run: xcrun metal --version I get: error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain I tried: sudo xcodebuild -downloadComponent MetalToolchain but it just stays on: Beginning asset download... If I cancel it, I get: xcodebuild: error: Download was cancelled. (Asset download for com.apple.MobileAsset.MetalToolchain ...) I've also run: xcodebuild -runFirstLaunch and installed the latest Command Line Tools for Xcode 27.0 through Software Update. xcrun --find metal does find the executable, but the actual Metal Toolchain appears to be missing. I'm mainly trying to get this working so I can use Unreal Engine 5.6. Has anyone had this issue with Xcode 27, or know the correct way to install the Metal Toolchain when xcodebuild -downloadComponent gets stuck at "Beginning asset download"? Thanks!

Starting with Xcode 27, my attempt to start a debug session for my C++ project fails. The Run scheme used has the Console setting configured for "Terminal" fails. The Terminal opens, but there appears to be a failure in the execution of the 'darwin-debug' command in the shell spawned for the debug session: Here's the output in the Terminal: Last login: Sat Sep 19 13:46:54 on ttys001 /bin/bash -c 'arch -arch arm64 "/Volumes/MyPassport/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/darwin-debug" --unix-socket=/tmp/7RBHab --arch=arm64 --working-dir "/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --disable-aslr --env="OS_ACTIVITY_TOOLS_PRIVACY=YES" --env="OS_LOG_DT_HOOK_PREFIX=OSLOG-E37B26CB-6471-4B1C-ACB7-48236B4EC921" --env="TERM=dumb" --env="SHELL=/bin/zsh" --env="MTL_DEBUG_LAYER_VALIDATE_STORE_ACTIONS=0" --env="DYLD_FRAMEWORK_PATH=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="SWIFT_BACKTRACE=enable=no" --env="CA_ASSERT_MAIN_THREAD_TRANSACTIONS=0" --env="CFLOG_FORCE_DISABLE_STDERR=1" --env="__XCODE_BUILT_PRODUCTS_DIR_PATHS=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="IDE_DISABLED_OS_ACTIVITY_DT_MODE=1" --en% paulrockwell@Upstairs ~ % /bin/bash -c 'arch -arch arm64 "/Volumes/MyPassport/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/darwin-debug" --unix-socket=/tmp/7RBHab --arch=arm64 --working-dir "/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --disable-aslr --env="OS_ACTIVITY_TOOLS_PRIVACY=YES" --env="OS_LOG_DT_HOOK_PREFIX=OSLOG-E37B26CB-6471-4B1C-ACB7-48236B4EC921" --env="TERM=dumb" --env="SHELL=/bin/zsh" --env="MTL_DEBUG_LAYER_VALIDATE_STORE_ACTIONS=0" --env="DYLD_FRAMEWORK_PATH=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="SWIFT_BACKTRACE=enable=no" --env="CA_ASSERT_MAIN_THREAD_TRANSACTIONS=0" --env="CFLOG_FORCE_DISABLE_STDERR=1" --env="__XCODE_BUILT_PRODUCTS_DIR_PATHS=/Volumes/MyPassport/paulrockwell/Library/Developer/Xcode/DerivedData/GNU_APL-gulwhsgobkphkodqgsftvqohegyk/Build/Products/Debug" --env="IDE_DISABLED_OS_ACTIVITY_DT_MODE=1" --en There appears to be a missing single quote in the command line, but if I complete it, darwin-debug fails to start with the following error message: darwin-debug: option `--en' requires an argument This worked on Xcode 26. Any thoughts on what might have changed and can I update the project to get around this? This issue is happening on any C++ project that I've created on prior versions of Xcode. And yes, I need to debug operation of one of the projects using the Terminal - the one project I'm interested in is GNU APL, which makes heavy use of terminfo and alternate character sets in its operation.

xcode cannot startup xcode cloud.

I'm trying to test on the new iPhone Duo simulator (Xcode 27.1 beta), but I cannot find a way to unfold the device anywhere in the Device Hub. The floating posture widget that is supposed to appear at the bottom center of the window simply isn't rendering for me. I thought it might just be hidden, but I've combed through the entire macOS menu bar (Device, Controls, View, etc.) and the options to change the fold state are completely absent from the dropdowns as well. Has anyone else run into this UI bug? Is there a hidden setting to toggle the posture controls back on, or a keyboard shortcut to force the simulator into its flat full-screen state in the meantime? Any help is appreciated!

I have a problem downloading Xcode components like Metal Toolchain or Developer Documentation. The action stuck with the status "Preparing to download". The symptoms started several weeks ago. I noticed this when my copy of Xcode 27 beta stopped showing the developer documentation. Strangely, when I re-launched Xcode it insists to download the Developer Documentation and keep showing "Preparing to download" while other components like Metal Toolchain, when I quit Xcode, it cancels the component download and that component status reverts to "Get". The symptoms continue thru the released version of Xcode27. Does anyone know the cure?

I have been struggling with this for a while and have gone through every solution I have found on the forums, so I am hoping someone at Apple or in the community can shed some light on the actual root cause. Setup Mac: macOS 26.7 (Build 25G229) Xcode: 26.2 (Build 17C52) — also tried 16.8 and 26.0, same result Device: iPhone SE (3rd generation), iPhone14,6 — iOS 26.7 (Build 23H24) Developer Mode: enabled on device Pairing state: paired, tunnel connected The error When I connect my iPhone via cable, Xcode initiates pairing and device preparation, then immediately fails with: The developer disk image could not be mounted on this device. Domain: com.apple.dt.CoreDeviceError Code: 12040 Failure Reason: Unable to find a valid DDI for the iOS platform. Run 'devicectl list preferredDDI' from the command line to get more details. User Info: { DVTErrorCreationDateKey = "2026-09-22 17:14:25 +0000"; DeviceIdentifier = "3B75FE83-5833-53B2-8ABE-9AA65A22A1C8"; "com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI; } Underlying errors: Code 12001 — Unable to find a valid DDI for the iOS platform. Code 12007 — Unable to find a developer disk image to use for the iOS platform (variants: Internal, Public). Diagnosing: no DDIs found for any platform Running the suggested command: xcrun devicectl list preferredDDI Output: Failed to load provisioning parameter list due to error: Error Domain=com.apple.dt.CoreDeviceError Code=1002 "No provider was found." UserInfo={NSLocalizedDescription=No provider was found.} Host CoreDevice version: 518.27 WARNING: No DDI was found for the iOS platform. No DDI was found for the macOS platform. No DDI was found for the tvOS platform. No DDI was found for the watchOS platform. No DDI was found for the visionOS platform. The key signal here is Code=1002 "No provider was found." — this same error appears as a prefix in every devicectl command I run, regardless of the subcommand. I suspect this is the actual root cause, not a secondary issue. Additionally, /Library/Developer/DeveloperDiskImages does not exist on this machine. What I have already tried xcrun devicectl manage ddis update Updating host DDIs at /Library/Developer/DeveloperDiskImages The following directories provided candidate DDIs: /Library/Developer/CoreDevice/CandidateDDIs /Applications/Xcode-26.2.0.app/Contents/Resources/CoreDeviceDDIs After cleaning and updating the installed host DDIs in /Library/Developer/DeveloperDiskImages are equivalent to the original set. The command completes without error, but /Library/Developer/DeveloperDiskImages is still never created. Reinstalling Xcode system resources: sudo installer -target / -pkg $(xcode-select -p)/../Resources/Packages/XcodeSystemResources.pkg No change. Multiple Xcode versions — tested with 16.8 and 26.0 in addition to the current 26.2. Same failure across all. Multiple iOS versions on the device — the iPhone has been factory reset several times and tested on different iOS 26.x builds as Apple released them. Issue persists on all versions. Confirmed xcode-select -p points to the active Xcode installation and xcrun resolves tools correctly. Device info (for reference) xcrun devicectl list devices Name Identifier State Model iPhone de Carlos 3B75FE83-5833-53B2-8ABE-9AA65A22A1C8 connected (no DDI) iPhone SE (3rd generation) The device pairs and tunnels fine. The only blocker is DDI services (ddiServicesAvailable: false). Questions What does Code=1002 "No provider was found." actually mean in the context of devicectl? Is there a provisioning service or entitlement missing on the Mac side? Why does devicectl manage ddis update report success but never create /Library/Developer/DeveloperDiskImages? Is there a prerequisite directory or permission that needs to exist first? Is there a way to manually force-install the DDIs from the Xcode bundle, bypassing the update mechanism? Any guidance would be greatly appreciated. Happy to run additional diagnostics if needed.

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?

In Xcode's Settings → Intelligence section, there's no built-in AI agent/model available, only chat bots. I'm not able to download a model through the Components section as well, but no models are offered or downloadable there either. Environment: Xcode 26.6 and Xcode 27 beta 6 macOS 26.6.2 MacBook Pro (Apple M4 Pro)

After building our app with Xcode 27.0 (27A266a), we observed that it crashes immediately at launch on devices running iOS versions below 17. Devices running iOS 17 or later appear unaffected by this issue. The previous release, built with Xcode 26, worked on older iOS devices. Deleting and reinstalling the affected app does not resolve the crash. Build settings: Minimum deployment target: iOS 15.0 Swift language mode: Swift 5 Configuration: Release Two crash reports from iOS 16.3.1, covering separate app builds produced with Xcode 27, show the same error: Exception Type: EXC_CRASH (SIGABRT) Termination Reason: Namespace DYLD, Code 4, Symbol missing Symbol not found: _$ss12_ArrayBufferV19_getElementSlowPathyyXlSiFyXl_Ts5 Referenced from: Topi.app/Topi Expected in: /usr/lib/swift/libswiftCore.dylib (terminated at launch; ignore backtrace) The symbol demangles to: generic pre-specialization <Swift.AnyObject> of Swift._ArrayBuffer._getElementSlowPath(Swift.Int) -> Swift.AnyObject The system launch screen appears, then dyld terminates the process before application startup code executes. We have not yet isolated whether the reference comes from compiler-generated application code or a linked dependency, nor completed a same-source comparison between Xcode 26 and 27. Is this a known Swift runtime compatibility issue with Xcode 27 when targeting iOS below 17? Is there a supported fix or workaround that preserves iOS 15 and 16 support?