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?

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

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

Tried three times now and absolutely cannot get Xcode 27 to install iOS 27 Simulators. I have done a complete uninstall of Xcode (including things in ~/Library). And even purged /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/ When Xcode 27 (27A266a; release version) is installed and run the first time, I'm greeted with the SDK screen. I select iOS and it downloads that runtime. I can see it in Xcode's Components panel in Settings. I only see Any iOS Device as a target device in Xcode. If I launch Device Hub, it's empty and I cannot add any devices since the Add dialog shows No Runtimes Available. Selecting "Add Platforms in Xcode" takes me back to Xcode, but I only ever see iOS 26.5 or older in the list. I've even tried the various xcrun simctl commands, but to no avail. Why is it so difficult to have a clean install of Xcode 27, have it install the iOS 27 SDK and then be able to build and run existing projects? I'm on the release version of macOS 27.0.1 though the problems persisted earlier today on macOS 27.0 as well.

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

Each time I launch a Debug version of the app on iOS Simulator, I see the Launch Screen presented and then about a 30-second delay before the app is responsive and debug output appears in the console panel. Filed FB22345091

Since Xcode 27 GA, text entry from a UI test on a physical iOS 27 device delivers only the first 3–4 characters and then stops, while the call still returns success. Taps and scrolls are fine. The same tests pass on Xcode 27 beta 1. Filed as FB24932647. Broken: Xcode 27.0 (27A266a), 27.1 beta (27A9269), 27.2 beta 2 (27B5028f) Works: Xcode 27 beta 1 (27A5194q) Device: iPhone, iOS 27.0 (24A437) Repro. We drive it through WebDriverAgent. The failing step is XCTest's own event synthesis in testmanagerd, which is the same path XCUIElement.typeText goes through. Xcode 27.2 beta 2, run sudo xcodebuild -runFirstLaunch, reboot the device. Type subjectline into a plain UITextField. Read the field's value back. Expected subjectline. Actual sub or subj, in every one of 16 attempts. In a recipient-style field the fragment appears and is then erased, so nothing survives. 0 of 32 attempts completed. Device log, all within one second: testmanagerd Failed to load displays from CADisplay testmanagerd Failed to resolve displays. Defaulting to generic keyboard sender. testmanagerd Recap event action playback initiated UIKitCore hardwareKeyboardAttached = YES UIKitCore Moving from placement OnScreen to OffScreenDown UIKitCore Change to input view set: (empty) testmanagerd Recap event action playback completed testmanagerd can't resolve a display, so it falls back to a generic keyboard sender that registers a virtual HID keyboard. iOS then treats that as a hardware keyboard and dismisses the software keyboard while the text is still being typed. What changed. Comparing testmanagerd in the two DeveloperDiskImages: beta 1 derived the display from the app's identity (Computed display ID … from embeddedApplicationIdentifier … bundleID). GA removed that and added CADisplay enumeration with the generic fallback. That code is unchanged through 27.2 beta 2. This is not 181945323, which is marked fixed in 27.2 beta 2. That one needs Device Hub and clears on its own. Is anyone else seeing this on device? Is there a supported way to type on device under Xcode 27 GA, other than staying on beta 1?

iOS app installation fails with 0xe8008018 for company team, but succeeds with another Apple Account Hello Apple Developer Community, We are facing a persistent code-signing issue while installing iOS development builds on a physical iPhone. We have contacted Apple Developer Support multiple times, but we have not yet received a technical explanation for the root cause. Environment Xcode: 26.6 (Build 17F113) macOS: 26.5.2 (Build 25F84) Device: iPhone 12 Pro Max (iPhone12,5) iOS: 26.5 (Build 23F77) Company Team ID: T6MQ4RXG46 Development certificate: Apple Development: Muthoot Money Limited (3MH4U8W7M5) Error message When installing the app through Xcode, installation fails with: 0xe8008018 — The identity used to sign the executable is no longer valid. The full error also contains: MIInstallerErrorDomain Code=13 CoreDeviceError Code=3002 IXUserPresentableErrorDomain Code=14 ApplicationVerificationFailed Troubleshooting performed Verified that the development certificate is within its validity period. Checked the provisioning profile's expiration date and confirmed that the test device UDID is included. Verified the app signature locally using codesign --verify --deep --strict. Confirmed that the app's signing authority and TeamIdentifier match our company team. Tested both our existing application and a newly created minimal iOS project named SigningTest. Important finding The newly created SigningTest app also fails to install when signed using our company team. However, the same test app installs successfully on the same iPhone when signed using another Apple Account's team. This suggests that the issue may be related to the company team's signing configuration or another team-specific factor, although we have not identified the root cause. Questions What could cause iOS to reject a locally valid app signature with error 0xe8008018? How can we identify the specific certificate, provisioning, trust, or device-verification check that is failing during installation? Is there any additional diagnostic command or device log we should collect? Could this indicate a team-specific signing issue that requires investigation by Apple? We would appreciate any technical guidance from developers who have encountered and resolved the same error. Thank you.

Hello, I am experiencing an issue when running an iOS application on an iOS 17.x Simulator using Xcode 27.1. The simulator becomes completely unresponsive to user input, whether my application is running or not. I cannot type anything or interact with the screen, including tapping UI elements. However, I can still switch between Light and Dark Mode, and the appearance changes accordingly. This makes it impossible to test my application on iOS 17.x using the simulator. Has anyone experienced a similar issue with Xcode 27.1 and the iOS 17.x Simulator? Is there a known workaround or configuration that could resolve this? Any help or suggestions would be appreciated. Thank you.

Using Xcode 27.1 RC, the iPhone Duo simulator (Device Hub) only comes with the Settings and Safari apps. Am I missing something? Are there plans to have the usual simulator apps such as Photos, Calendar, Reminders, Maps, etc.? In these early stages it would be really nice to have some real apps to look at for examples of how some things should work/appear on the Duo in different layouts.

Where did the simulator "Slow animations" mode go? I can't find it in the Xcode 27 beta 2 "Device Hub". This feature is incredibly useful. I'm assuming it's a glitch that it's missing, or I'm just not looking in the right place.

I am rather flabbergasted by the “future Xcode project file format” error. It happens in Xcode 26: Indeed the project was maintained so far in a 27, nevertheless, the project format is set to **16**: Can please someone explain the culprit and suggest a fix? Thanks!

I've still an old iPhone X (running iOS 16.7.16) and like to also use this to test/debug my Apps, but it seems that XCode 27.1 does no longer support it. The device simply does not show up in the new Device Hub. I still have some App-specific data on this device, which I would like to use for the tests, but as XCode now ignores this device, I can't even copy the data over to the newer devices. Is it somhoe possible to add the device to the device Hub, or make it available to XCode so I can actually test on this device as well?