Environment Mac mini with Apple M4 macOS 26.7.2 (build 25G332) Xcode 26.6 CoreSimulatorService 1051.55 External USB SSD formatted as APFS, mounted read/write, with ownership enabled Source simulator: iPhone 17 Pro running iOS 26.5, shut down Issue I am attempting to preserve a shutdown simulator using the supported simctl clone operation, with the destination CoreSimulator device set located on an external APFS SSD. Command form: xcrun simctl clone <source-UDID> "<preserved-device-name>" "/Volumes/<external-volume>/<device-set-path>" The destination directory is owned by the logged-in user and has ordinary writable POSIX permissions. The volume is mounted read/write with ownership enabled. No restrictive ACL entries or file flags were found on the destination directories. Observed result simctl reports: NSPOSIXErrorDomain Code=22: Device was allocated but was stuck in creation state. CoreSimulator records the preceding data-clone failure as: NSCocoaErrorDomain Code=513 Underlying NSPOSIXErrorDomain Code=1 Operation not permitted The temporary destination simulator entered the Creating state and CoreSimulator automatically rolled it back. At the same timestamp, unified logging attributes the rejected external-volume write to com.apple.CoreSimulator.CoreSimulatorService, rather than to simctl. The TCC and sandbox sequence shows: A check for kTCCServiceSystemPolicyAllFiles. A check for kTCCServiceSystemPolicyRemovableVolumes. Removable-volume access requiring a TCC prompt. Prompting being denied because the requesting CoreSimulatorService is an Apple platform binary. Launch Services being unable to create an application record for the CoreSimulatorService XPC bundle. No consent prompt was displayed. CoreSimulatorService's Info.plist contains an NSRemovableVolumesUsageDescription string specifically describing access when a simulator device set is configured on external storage. This is a development-tool/service issue; no application project or third-party framework is involved. Expected result CoreSimulatorService should either present or arrange the supported removable-volume consent workflow, or use a documented user-controlled Files & Folders permission that allows an external device set. Questions What is the supported procedure for granting SystemPolicyRemovableVolumes access to com.apple.CoreSimulator.CoreSimulatorService when the Apple platform XPC service cannot display the consent prompt? Should CoreSimulatorService appear in System Settings > Privacy & Security > Files & Folders with a Removable Volumes switch? Is cloning into an external APFS CoreSimulator device set supported with Xcode 26.6 on macOS 26.7.2? Is there a supported way to initiate the operation so consent is attributed to Xcode or another user-facing Apple process? Is the Launch Services application-record failure expected, or is this a known CoreSimulator/TCC issue with an available fix? I have not edited the TCC database, reset privacy decisions, granted broad Full Disk Access, disabled security controls, changed permissions, removed extended attributes, manually copied protected simulator records, or retried using an unsupported filesystem workaround. I can provide focused, redacted CoreSimulator, sandboxd, and tccd excerpts privately if an Apple engineer requests them.

I am seeking a supported public diagnostic or prerequisite for a standalone Siri UI test. Feedback: FB25377231. Developer Technical Support directed this question to the forums. Environment: Mac mini (2024), Apple M4, 32 GB, native arm64 macOS 26.7.2 (25G332) Xcode 26.6 (17F113), iOS Simulator SDK 26.5 iPhone 17 Pro Simulator; the original test's xcresult identifies iOS 26.5 (23F73) Classic Siri, en-GB A small test-host project compiled and ran one selected XCTest case. Its core public API call was: XCUIDevice.shared.siriService.activate( voiceRecognitionText: "What is two plus two?" )The exact recognition text reached the testing activation path, but SpringBoard logged: No network. Not starting the request for SASRequestSourceTestingNo arithmetic answer appeared during the configured 30-second wait. This was observed once; a repeatable frequency is not established. This reproducer has no product app, app-specific Siri intent, or CarPlay integration. In the original Simulator test runner, the first unconstrained NWPathMonitor callback was satisfied, with en0/wiredEthernet, but supportsIPv4, supportsIPv6, and supportsDNS were all false. Default-route SCNetworkReachability samples reported reachable. A separate, later diagnostic used the same simulated device with the installed iOS 26.5 (23F77) runtime. Identical public Foundation/Network helpers on the host and Simulator each issued one URLSession HEAD request to: https://www.apple.com/library/test/success.html Both received HTTP 200. The Simulator helper's initial path callback again reported satisfied with IPv4/IPv6/DNS capability flags false. This proves a response only for that helper/API/URL/time. It does not prove that the flags stayed false, that a fresh DNS lookup occurred, that Siri endpoints were reachable, or that the earlier 23F73 failure had the same cause. A setup confounder may matter: additional iOS platform support, including runtime 23F77, was installed while the original 23F73 Simulator remained booted. The arithmetic test ran afterward but still reported 23F73 in xcresult. The later HTTPS control ran separately on 23F77. There has been no further Siri activation. What supported Simulator/XCUISiriService prerequisite or public diagnostic can distinguish the cause of this specific request-start refusal? Is it expected for this configuration, a known issue, or evidence of an unmet prerequisite? The complete original results and a minimal test-host project are retained. Selected evidence and source are already attached to FB25377231; the same material can be supplied privately to DTS. I am seeking a supported approach rather than private preferences, service overrides, or repeated test requests.

My paired Apple Watch never shows up in Xcode, so the Developer Mode toggle never appears on the watch (Settings > Privacy & Security). The paired iPhone works perfectly, and I build and install to it every day. Setup Mac: macOS Tahoe 26.6, Xcode 27.0 (watchOS 27 SDK and platform installed) iPhone 15 Pro Max, Developer Mode ON, shows as connected in xcrun devicectl list devices over USB Apple Watch on watchOS 26.x, passcode set, unlocked, on wrist Free personal team (also tried a second free Apple ID; both are signed in to Xcode) Symptom xcrun devicectl list devices lists the iPhone and an iPad, never the watch Devices and Simulators shows no watch under the iPhone No ~/Library/Developer/Xcode/watchOS DeviceSupport folder has ever been created Unified log on the Mac shows no CoreDevice / remotepairing activity for the watch at all. It looks like the Mac never hears from it. Network No router. The Mac gets internet from an iPad over USB and re-shares it over Wi-Fi (macOS Internet Sharing). iPhone and watch are joined to that network. I also tried the Mac and phone on the iPhone's Personal Hotspot. VPN is off and the firewall is off. Already tried, no change Unpaired the watch and paired again (restored from backup) iPhone: Settings > Developer > Clear Trusted Computers, re-trusted, xcrun devicectl manage pair Accepted the "Trust this computer" prompt on the watch after a restart iPhone Developer Mode off, restart, on, restart Signed out of and back in to Xcode accounts; accepted the latest agreements Restarted the Mac, iPhone and watch; waited 5+ minutes with the Devices window open each time Bluetooth and Wi-Fi on everywhere; watch and Mac on the same Wi-Fi Is there a way to force Xcode to discover the watch through the iPhone, or a log predicate that shows why the watch is never offered? Any pointers appreciated.

It doesn't show any files, only warning or errors for me. Same behavior with @

Hi everyone, I'm experiencing an issue with the OpenAI integration in Xcode 26.3. When I navigate to Xcode → Settings → Intelligence → OpenAI, Codex is marked as "Unavailable", and I cannot download or enable it. My configuration: macOS: 26.7.2 Xcode: 26.3 Apple Intelligence: Enabled ChatGPT Plus subscription: Active ChatGPT in Xcode: Available and working Claude integration: Available and can be downloaded normally Codex: Unavailable I've attached a screenshot showing the issue. I'm wondering why Codex is unavailable while Claude works without any problems, despite Apple Intelligence being enabled. Has anyone encountered the same issue? Could this be related to regional restrictions, compatibility requirements, or an Xcode bug? Any help or suggestions would be appreciated. Thanks!

I am using Coding Intelligence, powered by Claude, in the first production release of Xcode 27.0 (in MacOS 26.7). Initially it was working ok. But after less than a day, it now crashes every time it needs to ask for permission for any shell command. And each time I restart things, it burns through a ton of tokens. ☹️ Any suggestions? (I'll file a bug report right now…)

Seriously, how come that Xcode has to do everything the wrong way, in the opposite to every normal IDE and solution that has been introduced over 10 years ago. We have been dealing for so many years with the insane xcodeproj format, so to ease the pain they've introduced JSON format. Sounds like an improvement, right? Not really, instead of using regular JSON, they decided to use JSON5 making it icompatible with 95% of CLI tools & automations like the famous jq tool. They could have solved all the issues with xcodeproj, but they decided to only make PRs more readable and introduce thousand other issues which will require building another wrappers and tools to manage the project format. On top of that, they're building CLI tool to interact with the project: xcrun xcodeproj, but instead of providing the output in a parsable way like using regular JSON (like every normal CLI tool would), they print everything in human-redable way in columns, etc. which makes parsing it miserable. I can't comprehend how it happens that they don't learn from their own mistakes of reinventing the wheel by using rectangular shape...

We are installing Xcode for standard users, but as the standard users don’t have admin rights, they cannot install the system wide components they need admin access to do that, but we don’t want to grant admin access to our users. We have already developed a script where we are accepting the license and we are doing the run first launch, but they still need the iOS simulator and the other packages pre-installed, so how can we do that?

Currently, we do not have a way to open, close and rotate iPhone Duo devices via XCUITest test automation. Please provide a way to perform these operations via XCTest. XCUIDevice.shared.orientation has no effect on an iPhone Duo iOS 27.1 simulator. We could open, close and rotate an iPhone Duo simulator manually via the Device Hub at the moment.

How can I test tent mode and other poses with iPhone Duo in Device Hub?

I am a long time developer but have never incorporated an IAP into any of my work so this is very new to me. So to save time I have used some AI for coding, but the code is having an issue and I'm not sure whether it is in the code or in Xcode. Xcode 27 on macOS 27.0.1 for iOS 27.0.1. IAP is to unlock full access after a 14-day trial. DESCRIPTION OF PROBLEM In local Xcode StoreKit testing, Product.purchase() returns .pending (as expected, since "Ask to Buy" is enabled), and Xcode’s transaction manager continues to show “Pending Approval.” After closing and reopening the app’s purchase sheet, the same transaction appears as verified and non-revoked in Transaction.currentEntitlements and is delivered through Transaction.updates, giving full access to the app. This reproduces in a standalone UIKit test app (linked below). The source file in question is AppAccessManager.swift. The relevant functions are: AppAccessManager.purchaseProduct() Calls product.purchase(). Handles .pending by recording a request reminder and displaying feedback. AppAccessWindowViewController.viewDidLoad() Runs when the purchase-options sheet is opened. Calls manager.start() followed by manager.refreshAccessState(). This is the sheet-opening path associated with the unexpected transaction delivery. AppAccessManager.refreshAccessState() Iterates Transaction.currentEntitlements. A transaction still labeled “Pending Approval” in Xcode is returned here as verified and nonrevoked. AppAccessManager.startListeningForTransactionUpdates() and handleTransactionUpdate(_:) The same pending transaction is also delivered through this sequence as verified and nonrevoked. The handler applies access before calling transaction.finish(). AppAccessManager.applyVerifiedPurchase(_:) Applies verified transactions received from successful purchases or the listener. STEPS TO REPRODUCE https://avliscoding.com/storekittest.zip Launch app Select "Open Purchase Sheet" Start trial Quit app, enable "Ask to Buy" in StoreKit file configuration settings Restart app. Select Purchase (will give a pending message in response) Close sheet Reopen sheet The app now believes it has made that purchase even though the purchase is still "Pending" in Xcode.

When using the canvas with a iPhone Duo running 27.2 the toolbars show up at the top. Had this issue with 27.1 as well. when i run the app in Device Hub or on a real device the toolbars correctly show on the side. I have downloaded 27.2 components so thats done. I would like the canvas to show the toolbars correctly. Any advice would be appreciated.

I'm trying to test the new “Describe a Shortcut” feature in iOS 27 using an iPhone 17 Simulator. When I open Shortcuts and tap “Describe a Shortcut”, it stays on: “Preparing support for describe a shortcut” and the text field remains disabled. I cannot enter anything or create the shortcut. My setup: Mac: MacBook Pro macOS: 27 Xcode: 26.5 (17F42) Simulator: iPhone 17 iOS: 27 I also have a physical iPhone 14 Pro, but I understand that it doesn't support Apple Intelligence, so I'm trying to test this using the iPhone 17 Simulator. Do I need to enable/download anything for Apple Intelligence on the Mac or Simulator? Or is “Describe a Shortcut” currently unsupported/not working in the iOS 27 Simulator? Any guidance on the correct setup would be appreciated.

I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators. Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app. Issue A (when Watch is visible in Xcode) In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect. Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.” In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation. Issue B (after unpairing Watch in Xcode only) I unpaired/removed the Watch in Xcode (Devices & Simulators). I did not unpair the Watch from the iPhone. Now: iPhone appears in Xcode and works normally for builds. Watch is still paired to the iPhone and works normally. Watch no longer appears anywhere in Xcode Devices & Simulators (no paired watch section, no watch run destination). What I’ve tried Reboots of Mac, iPhone, Watch (multiple times) Watch unlocked, awake; iPhone unlocked and close to Watch Verified Watch is paired and connected in iPhone Watch app Developer Mode enabled on iPhone and Watch Wi-Fi and Bluetooth ON (Mac/iPhone/Watch), tried toggling both Tried on home Wi-Fi and also with iPhone hotspot (same result) Resetting trust prompts / reconnecting iPhone via USB, re-trusting Mac Apple Watch: “Clear Trusted Computers” Xcode: removing/re-adding devices; clearing derived data; restarting Xcode Watch Developer networking test: Responsiveness = Medium (430 RPM) Questions 1. Is this a known issue/regression with Xcode 26.2 + watchOS 26.2 tunneling (CoreDevice / devicectl)? 2. Is there an Apple-supported way to force Xcode to re-discover a paired Watch after it was removed from Xcode Devices & Simulators (without unpairing the Watch from the iPhone)? 3. Any recommended logs or diagnostic steps I should collect (Console logs, sysdiagnose, specific Xcode/CoreDevice logs) to include in a Feedback report? If helpful, I can provide the full error text from Xcode’s Devices window and any logs you recommend. Thank you in advance,

The live Device Hub window shows my app's colors differently from a physical iPhone. The pixel values themselves are correct: a screenshot taken in Device Hub has the same colors as the device. Only the live window looks different — [e.g. more washed out / more saturated]. It happens in every project I've tried, including ones that use only plain sRGB colors and sRGB image assets, so it doesn't look app-specific. Setup Xcode 27.0 (27A266a) MacBook Pro, Apple M4 Max Built-in Liquid Retina XDR display (default "Color LCD" profile) and an external BenQ PD2705UA Simulated devices: iPhone 13 mini (iOS 26.1) and iPhone 14 (iOS 26.5) What I've ruled out Same result on both the built-in display and the external monitor True Tone and Night Shift are off on the Mac The simulated device is in light mode, with Increase Contrast, Invert Colors and Grayscale off The Device Hub screenshot matches the physical iPhone, so the rendered pixels are correct Questions Is the Device Hub window color-managed for the Mac's display, or is this expected behavior? Is there a setting to make the live window show accurate colors?

The Photos app in the iOS simulator instantly crashes when attempting to drag an image to another app in Split View mode. I’m using Xcode 15.4 (15F31d), which is the current App Store build and the iOS 17.5 runtime, running on an Intel MBP. N.B.: This is drag-dropping between apps in the simulator, rather than from macOS into the simulator. Is this a known issue?

The simulator and interface builder in Xcode 26.3 can not dispaly emojis, but macOS Sequoia highest supported version of Xcode is 26.3, and my iMac highest supported macOS is macOS Sequoia, so is it possible to provide a update for Xcode 26.3 for macOS Sequoia to fix this bug?

I'm getting persistent backboardd crashes in the iPadOS 27 simulator when my app and another app (Safari, Photos or Calendar, etc.) has windows visible on the screen at the same time, including slide over, etc. Steps to reproduce: Launch my app in an iPadOS 27 simulator. Open Safari or Photos in another window. Arrange both app windows so they're visible. Within a second backboardd crashes with EXC_CRASH (SIGABRT) in a com.apple.coreanimation.display.primary thread. The simulator log reports… -[MTLTextureDescriptorInternal validateWithDevice:]: error 'Texture Descriptor Validation MTLTextureDescriptor has invalid pixelFormat (0).' Xcode subsequently reports connection-interrupted messages and ends the app's debug session with: “Debug session ended with code 9: Terminated due to signal 9.” This works correctly in iPadOS 26.x simulators and on a physical device running iPadOS 27. I can reproduce this with both Xcode 27 and 27.1. Resetting the simulator and testing different simulated iPad models does not resolve it. Is anyone else seeing anything like this? It's presumably something I'm doing wrong, so I've double checked my UIScene handling and all seems well (it's been in there for a while) so I'm somewhat at a loss as to where to look next. This is on a Mac Mini M4 Pro running macOS 27.0.1 (26A434).

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

Uploading an iOS app built with the public release of Xcode 27.2 (27B52) fails with this error (code 90534 / ITMS-90534 in the upload logs): Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn't supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. The upload itself completes; the error is returned afterward by App Store Connect when Xcode checks the upload's status, so this looks like server-side validation not yet recognizing the final 27B52 build. As of today, developer.apple.com/news/releases lists Xcode 27.2 RC (27B48) but not Xcode 27.2 (27B52). Archive metadata (app and all extensions match): DTXcode: 2720 DTXcodeBuild: 27B52 DTSDKName: iphoneos27.2 DTSDKBuild: 24B8118 Deployment target: iOS 26.0 No embedded third-party frameworks Uploaded via Xcode Organizer (ContentDelivery 27.10.4-2.2), macOS 27.2 (26B123) Local setup checked: Only one Xcode installed (27.2, 27B52); xcode-select points to it; no DEVELOPER_DIR or SDKROOT overrides Reproduced after a clean build and a fresh archive Upload error IDs: JITIPJCXJDJFKY7RQZS6GAWAGM (Oct 30, 2026) 2D3BNQAYTYPEPADRSCS4XCHZME (Oct 30, 2026, after a clean rebuild) Can Apple confirm whether Xcode 27.2 (27B52) is accepted for App Store submission, or whether builds should use 27.2 RC (27B48) until it is?