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.

I am writing this post while I wait for the progress to move from 0% to 3%. Did someone find a way to speed this up? It is a nightmare experience that Apple provides to developers aiming at Watch.

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

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.

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!

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?

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.

I just downloaded and installed the final released Xcode 27.2, and it queued up, downloaded, and installed not one but two simulator SDKs. Why is that?

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?

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?

SUMMARY In Xcode 27.1, opening any Main.storyboard never finishes loading. The editor shows "Loading iOS 27.1..." indefinitely. This happens in existing projects and in a brand-new iOS App project created with Interface: Storyboard. Before that, the editor showed "Failed to open Main.storyboard: iOS 27.1 Platform Not Installed." ENVIRONMENT Xcode 27.1 iOS SDK build: 24A94232 (from xcrun --sdk iphonesimulator --show-sdk-build-version) macOS: [YOUR macOS VERSION] Hardware: MacBook Air, Apple M1 Run destination: iPhone 17 Pro Max simulator STEPS TO REPRODUCE Open Xcode 27.1. Create a new project: iOS > App, Interface: Storyboard, Language: Swift. Click Main.storyboard in the Project Navigator. EXPECTED RESULT The storyboard renders in Interface Builder and the Objects library lists UI elements. ACTUAL RESULT The editor stays on "Loading iOS 27.1..." and the Objects library shows "No Matches." Opening the file as Source Code works, and the XML is valid (targetRuntime="iOS.CocoaTouch"), so the file itself is fine. RUNTIME STATE Initially the only iOS 27.1 runtime installed was build 24A94425, shown as Ready in xcrun simctl runtime list. Xcode reported "iOS 27.1 Platform Not Installed," and the runtime did not appear in Settings > Components. The Xcode SDK build is 24A94232, which does not match 24A94425. I ran xcodebuild -downloadPlatform iOS, which installed iOS 27.1 (24A94232). The error then changed to "Loading iOS 27.1..." and stayed there. Settings > Components then showed an "Update" button for iOS 27.1 (8.07 GB). Clicking it installed iOS 27.1 (24A94425) again, so both builds are now present and Ready. The storyboard is still stuck. WHAT I TRIED (none fixed it) Deleting ~/Library/Developer/Xcode/DerivedData sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService Removing and reinstalling the iOS 27.1 runtime Restarting the Mac Waiting several minutes on the first load (~/Library/Developer/Xcode/UserData/IB Support does not exist on this machine) [link text](https://www.example.com/)

Does Xcode 27 or TestFlight support installing a watch-only beta on an Apple Watch For Your Kids device? I want to test my watch only standalone app on my kids apple watch as that is the only device I have. Is it possible to use that watch for testing standalone apple watch application. The watch is setup as kids watch on my iphone.

In a synthetic reproduction of a DeviceSupport-style backup on macOS 26.7.1 with Xcode 26.6 on Apple silicon, a source object has no com.apple.provenance, while a newly created destination object acquires that private extended attribute. File contents, modes, ACLs, and the source's other extended-attribute names can be verified independently. The backup acceptance contract requires a future restore to reproduce the original governed metadata. Is destination creation expected to add this attribute? For a faithful restore to a fresh APFS destination, should restoration software omit it, remove it after creation, preserve it, or allow macOS to regenerate it? Which supported API or documented postconditions establish restoration fidelity when the source lacked the attribute? Could the attribute affect DeviceSupport symbol usability or access behavior? We are seeking Apple-supported backup and restoration procedures and security postconditions, not an interpretation of private metadata. No real DeviceSupport files, raw private attribute values, production paths, credentials, datasets, or personal information are included.

Trying to delete or replace appIcon in my project's assets.xassets fails. After a few seconds xcode displays error "...couldn't be moved to the trash because the volume Macintosh HD doesn't have one." Needless to say the trash folder exists and works from Finder. The volume has 97G free space. I tried xcode's 'delete derived data' and 'clean build folder' and restarted xcode. Same behavior (deleting appIcon fails).

I am qualifying a data-preserving update of my own development-signed iOS/iPadOS app (Target Keeper). I would like to understand the supported recovery guarantees and limitations before changing an existing installation, rather than treating a completed backup or successful model-open test as proof of full rollback. Environment: iOS/iPadOS 27.0.1 and Xcode 27.1. Existing development installations must be retained. The original signed packages for the older installed builds are unavailable. No update, uninstall, device erase or restore has been performed as part of this qualification. Evidence already retained privately: Completed encrypted Finder backup records for each device, with the password kept private. Apple Device Hub downloads of each existing app-data container, retained separately with file counts and SHA-256 manifests. Disposable copies of the actual prior SwiftData store, relevant WAL/SHM files, preferences and selected-photo data opened using the proposed version's existing model and guarded local-startup implementation. Model identities/content fingerprints were unchanged in those tests. The separate Codable Portfolio repository passed loading/reopening on disposable copies without changing the ledger bytes. Controlled process interruption/reopen tests passed on disposable local copies. These tests did not run the entire signed app-update lifecycle on a physical device, validate Keychain continuity, establish an atomic source-side multi-store snapshot, or test restore on the original devices. CloudKit records are not being mutated. I have read Apple's update-testing and container-download/replace guidance: https://developer.apple.com/documentation/xcode/testing-a-release-build https://help.apple.com/xcode/mac/current/en.lproj/dev816c242e1.html Specific questions: For a locally development-signed app that is not available from the App Store, what does an encrypted Finder backup preserve and what additional artifacts are needed to recover the usable app and its data if the original signed app package is missing? Does a backup completion record establish anything about restoration of that development executable? What consistency guarantees does Device Hub's app-container download provide when the app has multiple stores (SwiftData/SQLite with WAL, a separate JSON ledger, preferences and photos)? Is a quiescent/terminated app required, and what is the recommended way to qualify a coherent capture without modifying the original records? What is Apple's recommended recovery rehearsal on a disposable device/installation before an in-place update? Which identity, signing, file-protection and Keychain limitations must be considered, especially for ThisDeviceOnly items and same-device versus different-device restoration? Which preservation checks remain the developer's responsibility beyond successful container replacement or store opening? I do not want to mistake reinstalling an app binary for rolling back a migrated multi-store data set. Separately, an earlier strict source read rejected a file-metadata change, but its paired content hashes were not retained. I am not asserting an Apple defect, corruption or an identified writer, and newer successful copies cannot reconstruct that missing observation. Is there a recommended narrowly scoped Apple diagnostic for future capture that records before/after file identity and content consistency without weakening integrity rejection? No backups, passwords, personal device identifiers, private certificates, record contents or confidential logs are attached. I am seeking a supported qualification procedure, not instructions to bypass preservation safeguards or destructively test on the original devices.

Hi, xcodebuild -downloadPlatform iOS stays at "Preparing to download..." for the iOS 27.1 Simulator (24A94425). mobileassetd receives 0 bytes. Environment: MacBook Pro (M3), macOS 26.7.2, Xcode 27 Tried (no change): Reinstalled macOS from Recovery Safe Mode Reset Xcode preferences Network to Apple servers is OK This started in September when the iOS 27.1 beta Simulator install failed (low disk space). mobileassetd log: Failed to set xattr on '/System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/1d40f…asset' (errno 2) SecKeyVerifySignature failed: CSSMERR_CSP_VERIFY_FAILED GetDecryptionKey: Failed to obtain decryption key Is there a supported way to reset the MobileAsset state or install the runtime manually? Feedback: FB25345300 Thank you.

It has always been this way. But I wonder why? Having the minimal xcode project, if you building and archive with: xcodebuild archive -project sample.xcodeproj -scheme sample -configuration Release -destination 'generic/platform=macOS' -archivePath out/sample.xcarchive DWARF_DSYM_FOLDER_PATH='out/dsym'final xcarchive will have empty dSYMs directory. At the same time, out/dsym/sample.app.dSYM exists. So it turns out that dSYM generation respects DWARF_DSYM_FOLDER_PATH variable, but archiving operation - doesn't. From my point of view, this is not logical because I explicitly specified the location and this location works partially. Am I missing anything? Is there some other variables that controls where archiving searchs for dSYM? Because at this moment it looks like it is internally hardcoded to somewhat like "$(BUILD_DIR)/$(CONFIGURATION)" Any help is appreciated, Best regards!

not only that but a new instance is created every time xcode quits and restarts. each instance runs at min 100% cpu constantly even when xcode quit. my batter has been draining super fast since the last xcode update. xcode is listed under Using Significant Energy all the time, even when idle in background. and even after quitting. I thought this might just be stale information but my activity monitor shows xcode as using 8,778 power in the last 12 hours even tho i quit it last night. swift-frontend doesn't show power usage. but in the CPU usage i saw 3 instances of swift-frontend each running above 100% CPU. i force quit them and xcode finally disappeared from the USP list.

I'm a paid Apple Developer Program member. Apple Developer Support confirmed by phone that my account has no restrictions, but every development-signed app I install on my registered iPhone is rejected. Environment iPhone 17 Pro,1, iOS 27.0 (24A435), Developer Mode enabled Device registered and enabled in Certificates, Identifiers & Profiles Signed with Apple Development certificates (issuer: WWDR G3), iOS App Development profiles Error ApplicationVerificationFailed 0xe8008018: The identity used to sign the executable is no longer valid.On the device: "This app was not installed because its integrity could not be verified." Device log during installation installd(libmis): Performing online authorization. online-auth-agent: The server returned: {"actions":["REJECT_PROFILE"],"authorized":false,...} online-auth-agent: Permanently rejected profile: <hash, <profile UUID installd(libmis): No online authorization (0x2) installd(libmis): validation failed because of failing online authorization (-402620392)What I've ruled out Not certificate revocation: trustd reports OCSP status revoked=0 definitive=1 for the whole chain. Not app-specific: a brand-new, empty test app with a newly created App ID and a newly created development profile fails identically. Not certificate-specific: same result with two different Apple Development certificates, each in its own freshly generated profile (three profiles in total, all rejected). The provisioning profiles contain the device UDID and the signing certificate, and the app's entitlements are a subset of the profile's. Questions Under what conditions does the online authorization service return REJECT_PROFILE / authorized:false for a paid team whose account shows no restrictions? Is this a known issue with iOS 27 and development profiles? Since the device marks each profile as "permanently rejected", how can I restore authorization for my team on this device once the cause is fixed?

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...