FB22844728 Xcode 26.5, macOS 26.5, MacStudio M1 64 GB The disaster of S-L-O-W T-Y-P-I-N-G that plagued Xcode several years ago returns. I guess all the ultra-advanced LLM neuroneirowebs still can't advise those at Apple who develop the Xcode app how to provide this uber-exotic, unheard-of functionality: JUST TYPING THE CODE. This disaster doesn't affect all projects, but it does affect the exact one I'm working on, and I need to type a lot of code there. Significant time is already wasted. I performed all the recommended steps like relaunching, restarting, and deleting deprived data with no effect. Hope something can be done about it..

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/)

I have submitted a feedback report regarding Xcode 27.1 RC Device Hub: iPhone Duo screen captures function only work when the device is fully closed; alternative hinge positions produce a blank display.

This was maddening: I had written a very long and detailed prompt, then went to select "Codex" from the drop down menu at the top "start a new conversation", and it wiped out the entire prompt I was working on. Well, of course it did: that drop down is part of the "Start a new Conversation" icon button, but it's position is too far away from the actual icon to infer that is its purpose. It should be a popup that shows the current choice for model (GPT-5, GPT 4.1, Codex). ANOTHER lost prompt problem. If you have a prompt-in-progress (AI is maybe building some code), and Xcode crashes, it might not save that prompt for when you re-launch. And how might that happen? Well, there's still numerous ways using the coding assistanty might crash. One I've notice is if you switch out to another app, or if you invoke a screen capture, it might crash.

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.

Hello team, We are testing the Declared Age Range/Age Signal functionality in a TestFlight build and would appreciate guidance on the correct setup and testing process. Current Behavior Observed We are seeing inconsistent behavior between the Sandbox environment and the age-range results returned to the application. Scenario 1: Apple Account Signed In A regular Apple ID is signed in on the device. The TestFlight build is installed and launched. The application returns Verified Adult (18+). We then sign in to the Sandbox environment using a Sandbox Test Account and select a different test scenario (for example, a child/minor scenario). After relaunching the application, the age signal response still remains Verified Adult (18+). Scenario 2: Apple Account Signed Out We sign out of the Apple account from the device. As a result, TestFlight is also signed out. When the application is launched, the response changes to Unable to Verify. Even after changing Sandbox test scenarios (such as child, teen, or adult scenarios), the application continues to return Unable to Verify rather than the selected test case response. Based on this behavior, it appears that the application is not reflecting the scenario selected in the Sandbox environment. Questions What is the correct process for connecting an application to the Sandbox environment when testing Declared Age Range scenarios? Does the Apple ID used for TestFlight need to be associated with or match the Sandbox Test Account? Should the device remain signed in to a regular Apple ID while the Sandbox Test Account is used for testing? How does the app determine whether it should use the selected Sandbox scenario versus the signed-in Apple account? Are there any additional device settings, account requirements, or configuration steps required for Sandbox age-range testing? Is there a way to verify that the application is successfully connected to the Sandbox environment and consuming the selected test scenario? If the Sandbox scenario is configured correctly, should we expect the API response to change immediately when switching between child, teen, and adult test cases? At present, regardless of the Sandbox scenario selected, the application either continues to return Verified Adult (18+) or Unable to Verify, and we have been unable to validate the documented Sandbox test scenarios. Could you please provide guidance on the expected setup and testing workflow for TestFlight applications using the Declared Age Range feature? Thank you for your assistance.

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.

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?

I have a project that builds fine in macOS 26 with Xcode 26. On macOS 27 b4 and Xcode beta, the same project can't build because of a framework that should be pulled from a Swift Package from a package-registry (named Registry, for example below), hosted on JFrog. I have the registry set up and have the token in keychain. The resolution of the packages works. But when I build, I get error like this: error: Missing package product 'Registry.Package_Package.Package' (in target 'Target' from project 'Project') . The real package should just be 'Registry.Package'. Any help with that? Is it a bug?

Xcode is completely broken since I installed Xcode 27.1 Beta for the first time. Since then every Xcode I installed is unable to properly install simulators. Even though the SDK appears as installed in settings: Device Hub doesn't show it: To fix it I have to manually add SDK image using "xcrun simctl runtime add" and then play with a couple more commands. I've just installed Xcode 27.2 with iOS 27.2 SDK and again the same problem: There is a problem with signature: Any idea how to fix it, so that I don't have to install it manually every time...?

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)

On 25 October 2026, signing in to an Apple Account in the Simulator (Settings > Apple Account > Sign in Manually) fails on iOS 27.0 and iOS 26.5 runtimes (Xcode 27.1, macOS 27.0.1, Apple silicon), for a new account (SMS second factor) and for an established account (trusted-device second factor). The password and second-factor steps complete; then akd logs "Will check in with IDMS" and POST gsas.apple.com/grandslam/GsService2/postdata returns HTTP 401 with ec -22411, sec -42023 ("This action cannot be completed at this time"), followed by "Failed to check in with IDMS! ... AKAuthenticationError Code=-7026". Settings then says the account or password is incorrect. The host Mac checks in with IDMS successfully, and the account works on icloud.com. I need a second account in the Simulator to test CloudKit share acceptance. Is this a known issue, and is there a workaround? Feedback: FB25318712.

Hello, Turning on iCloud Drive sync does not work in iOS 27 simulators. When I sign into an iCloud account and try to enable it by tapping the switch in the iCloud Drive settings within the iCloud account area of Settings, the switch doesn't stay on and the feature is never enabled. I don't get an error or anything telling me what's going on. Anyone else seeing this? When I create a new simulator for iPhone 26.5 it seems to work fine just as before. I've tested this with Xcode 26.6 17F113 and Xcode 27 RC 27A266a.

Installed Xcode ProductBuildVersion 27A9275, SwiftBuild 25000.0.222. Synthetic static Swift framework and three arithmetic XCTest cases only. No real app, account, health data or code-signing identity is needed. A Seatbelt profile allows an exclusively owned child of the normal macOS per-user temporary directory, public SDK/toolchain reads and necessary build services, while denying private-home data and writes elsewhere. Network is denied. The process receives TMPDIR, TMP and TEMP set to that owned child. Fresh DerivedData and result-bundle paths also point inside it. A generic iOS Simulator build-for-testing stops at builtin-infoPlistUtility: mkdtemp tries to create swbuild.tmp.* directly in the per-user temporary parent and returns EPERM. The documented -userdefault=value argument syntax accepts -SWBBuildServiceEnvironmentOverrides='{ TMPDIR = "<owned-child>/"; TMP = "<owned-child>/"; TEMP = "<owned-child>/"; }' but a changed synthetic trial still selects the parent. Acceptance is not proof of the runtime dictionary type or transport adoption. A standalone process under the same profile, using installed Foundation, reports getenv("TMPDIR") as the owned child while both FileManager.default.temporaryDirectory and NSTemporaryDirectory return the parent. The installed SwiftBuild Path.temporaryDirectory implementation calls NSFileManager.defaultManager temporaryDirectory. The out-of-process initializer requires a string-to-string dictionary, then applies it to the child environment. Question for Apple: what supported per-invocation control makes built-in tasks use an explicitly owned temporary child on this version, and what supported no-build diagnostic proves its effective adoption? Is this Foundation behavior expected under Seatbelt? We cannot grant access to the shared parent or private home, change trust/keychain access, inject code, or modify installed libraries. CoreSimulator's separate runtime-availability error is not attributed to this temporary-path issue.

Hello, I am a beginner learning to develop iOS apps with SwiftUI. My setup: MacBook running macOS 27.0.1 Xcode 27.1 iPhone 15 Pro running iOS 27.0.1 Developer Mode enabled on the iPhone My iPhone is connected via USB-C and is recognized by Finder and macOS System Information. However, my iPhone does not appear as a run destination in Xcode. Only simulators are available. The command xcrun devicectl list devices detects the physical iPhone, but its connection information shows: pairingState: unsupported tunnelState: unavailable I have already restarted both devices, tried different USB ports, checked my Apple account in Xcode, and confirmed that Developer Mode is enabled. A simple SwiftUI test app runs correctly in the simulator, but I cannot install it on my physical iPhone. What could cause this pairing problem, and how can I resolve it? Thank you for your help.

Hello so i have been trying to download ios 27 simulator images in xcode but whenever i try to download it, it forever gets stuck in the state of preparing to download and never downloads it even after waiting for 2-3 hours, Can somebody please help me figure it out, i have tried uninstalling and reinstalling xcode but the issue isn't resolved please if someone has solution to this problem do share here!!