Hi everyone, I'm experiencing a persistent issue for months now where I'm unable to download the iOS 26 simulator Runtime. I've tried reinstalling Xcode and also Xcode Beta but same issue. iOS 26 Simulator is also not on developers download page, so manual installation is impossible. And sadly I can't compile any code without having iOS 26 simulator installed. Anyone able to get passed this? Hardware: M1 Pro OS: Tahoe 26.1 Heres the error Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2026-01-07 11:35:35 +0000"; } -- Download failed. Domain: DVTDownloadableErrorDomain Code: 41 -- Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({ RequestedBuild = 23C54; }) Domain: DVTDownloadsUtilitiesErrorDomain Code: -1 -- Download failed due to not being able to connect to the host. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 60 User Info: { checkNetwork = 1; } -- System Information macOS Version 26.1 (Build 25B78) Xcode 26.2 (24553) (Build 17C52) Timestamp: 2026-01-07T12:35:35+01:00

I have already paid the 99 USD for the enrollment, that was 8 days ago, I don't understand what is happening on the page it says that everything is managed in 48 hours... is there a problem? Additionally, I have generated a claim in Apple Support with caseID 102850171298 4 days ago, and it was not responded to in any way. I'm a little angry, it's not a cheap service and I have to work.

I am unable to use my iPhone 17 Pro as a run destination in Xcode. The device appears at a low level, but CoreDevice / devicectl keeps reporting it as unavailable. Environment • Mac mini (Apple Silicon) • macOS 26.3 (Build 25D125) • iPhone 17 Pro • iOS 26.3 • Xcode 26.3 (Build 17C529) • Xcode 26.4 beta 2 (Build 17E5170d) Symptoms • The iPhone appears in Finder • On the iPhone, I tapped “Trust This Computer” • Developer Mode is enabled • Apple ID is added in Xcode Accounts • Team is configured in Signing & Capabilities • iOS Platform Support is installed • The device still does not become available as a run destination • Devices and Simulators does not show it in a usable state • xcrun devicectl list devices still shows unavailable Output of xcrun devicectl list devices Failed to load provisioning paramter list due to error: Error Domain=com.apple.dt.CoreDeviceError Code=1002 "No provider was found." UserInfo={NSLocalizedDescription=No provider was found.}. devicectl manage create may support a reduced set of arguments. Name Hostname Identifier State Model CAC1B56A-C3B4-59FF-8F9D-659277C7C76C.coredevice.local CAC1B56A-C3B4-59FF-8F9D-659277C7C76C unavailable iPhone18,1 What I already tried • Apple cable • Different USB/Thunderbolt ports • Direct connection to rear ports • Restarted both Mac and iPhone • Restarted Xcode • Ran sudo killall usbmuxd • Ran sudo pkill -9 remoted • Upgraded Xcode from 26.2 to 26.3, then to 26.4 beta 2 • Ran sudo xcode-select -s /Applications/Xcode-beta.app • Ran sudo xcodebuild -runFirstLaunch • Reset “Location & Privacy” on the iPhone, then trusted the Mac again • Still remains unavailable Additional note ioreg shows the iPhone, so the physical USB connection seems to exist. However, at the CoreDevice / devicectl layer the device remains unavailable, and Xcode cannot use it for on-device build/run. Is this a known issue with macOS 26.3 / iOS 26.3 / Xcode 26.4 beta 2? Any workaround or additional debugging steps would be appreciated.

Hi. Our IT security team have flagged that on many developer machines they see a deprecated version of Python - 3.9.6. I've done some research on this and the general line is, feel free to upgrade the main version of Python on the Mac, but the version of Python which is internally used by Xcode (3.9.6) must be left unchanged. Our IT security team reached out to Apple and have received conflicting information as to if this Ruby 3.9.6 version can be upgraded. One response for example was "I asked my Solutions Engineer and he has come back with the following: We don’t include Python within macOS anymore, we install 3.9.6 with Xcode to support some of the internal tools - but there’s nothing preventing a customer updating that version: https://mac.install.guide/python/update". Does anyone know if it is possible to upgrade to a supported version? Kind regards, Kai.

It would be helpful to be able to edit forum posts for longer (ideally indefinitely) after posting and to have a GitHub issues style edit history. FB22328001 https://github.com/feedback-assistant/reports/issues/783

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.

I received the email confirming that I paid for my Apple account, but my account was never unlocked. I’ve already sent emails and requested phone support, but I haven’t been able to get help through any of these methods. I paid with my Visa card. Does anyone know what to do? Has anyone experienced this?

Hello, I am facing a critical issue where the Family Controls (Distribution) entitlement is not being applied to my app extensions, despite the main app ID being approved. Main App ID: com.hayashikento.focuspact (Approved on March 13) Extension ID 1: com.hayashikento.focuspact.ShieldActionExtension (Pending/Not visible) Extension ID 2: com.hayashikento.focuspact.ShieldConfigurationExtension (Pending/Not visible) I have submitted requests multiple times, but the entitlement does not appear in the "Capability Requests" for these extensions in the Certificates, Identifiers & Profiles portal. Furthermore, I am unable to contact Developer Support because the "Contact Us" form on the developer website consistently shows a "Request error" or freezes on the submission page. Since I am completely blocked from TestFlight distribution, could someone from Apple please look into my account (Team ID: UHG4J7F7NH) and manually sync these entitlements? Thank you for your help.

With the latest Xcode 26.4 my project fails to compile due to a "compiler unable to type-check in reasonable time" error with a library I've been using for years and has not changed. The library is https://github.com/ngageoint/mgrs-ios and is specifically around this line https://github.com/ngageoint/mgrs-ios/blob/master/mgrs-ios/utm/UTM.swift#L96. Since this isn't my library I can't change it, but again we've been using this library for years now without issue - it was only when Xcode updated this morning that our compilation workflow broke. (Compilation machine is an M3 Pro with 18GB of RAM, so I don't think that's the problem here)

After having built the SwiftUI project numerous times from Xcode and allowing the plugins after the first build post install using xcodebuild -scheme <SchemeName> build fails with: The following build commands failed: Validate plug-in “SwiftLintBuildToolPlugin” in package “swiftlintplugins” Validate plug-in “OpenAPIGenerator” in package “swift-openapi-generator” How are we supposed to grant the plugins permission to run in the CLI? Everything I'm getting from Gemini is for packages, not apps.

Hi, On a 1920 points wide monitor, running maximized, Xcode 26.4 can't show more than 10 editor tabs at a time. Under the same conditions, Xcode 26.2 adapts tab widths to file names and fits 12-14 tabs. That's 2-4 more files I can see and access at a glance, without extra interaction. How can I get that level of information density back in the Xcode 26.4 editor tab bar? Screenshots Xcode 26.4 (10 tabs) Xcode 26.2 (12 tabs) Xcode 26.2 (14 tabs)

I submitted this to Feedback Assistant as FB22331090 and wanted to share a minimal reproducible example here in case others are seeing the same issue. Environment: Xcode 26.4 or Xcode 26.3 Apple Swift version 6.3 (swiftlang-6.3.0.123.5 clang-2100.0.123.102) Effective Swift language version 5.10 Deployment target: iOS 17.0 The sample app builds successfully for normal development use, but archive fails. The crash happens during optimization in EarlyPerfInliner while compiling the synthesized deinit of a nested generic Coordinator class. The coordinator stores a UIHostingController. Minimal reproducer: import SwiftUI struct ReproView<Content: View>: UIViewRepresentable { let content: Content func makeUIView(context: Context) -> UIView { context.coordinator.host.view } func updateUIView(_ uiView: UIView, context: Context) { context.coordinator.host.rootView = content } func makeCoordinator() -> Coordinator { Coordinator(content: content) } final class Coordinator { let host: UIHostingController<Content> init(content: Content) { host = UIHostingController(rootView: content) } } } Used from ContentView like this: ReproView(content: Text("Hello")) Steps: Create a new SwiftUI iOS app. Set deployment target to iOS 17.0. Add the code above. Archive. Expected result: Archive succeeds, or the compiler emits a normal diagnostic. Actual result: The Swift compiler crashes and prints: "Please submit a bug report" "While running pass ... SILFunctionTransform 'EarlyPerfInliner'" The crash occurs while compiling the synthesized deinit for ReproView.Coordinator. Relevant log lines from my archive log: line 209: Please submit a bug report line 215: While running pass ... EarlyPerfInliner line 216: for 'deinit' at ReproView.swift:19:17 One more detail: The same sample archived successfully when the deployment target was higher. Lowering the deployment target to iOS 17.0 made the archive crash reproducible. This may be related to another forum thread about release-only compiler crashes, but the reproducer here is different: this one uses a generic UIViewRepresentable with a nested Coordinator storing UIHostingController.

Hello, I have a critical issue regarding the "Family Controls (Distribution)" entitlement. My app "FocusPact" was approved for the entitlement, but there is a technical mismatch in the Bundle IDs that prevents distribution via TestFlight. [Current Situation] Parent App ID: com.hayashikento.FocusPact (Approved / Capitalized) Approved Extension ID: com.hayashikento.focuspact.ShieldConfigurationExtension (Approved / Lowercase) [The Issue] Due to the case-sensitivity difference (FocusPact vs focuspact), Xcode throws a "Bundle identifier prefix mismatch" error. Since the parent app identifier is already established as capitalized, I cannot change it to lowercase without breaking the existing configuration. [Request] I have submitted a new entitlement request with the corrected capitalized Bundle ID: Corrected Extension ID: com.hayashikento.FocusPact.ShieldConfigurationExtension Could a DTS engineer please help me synchronize the approved status to this capitalized ID? This is purely a technical correction of an already authorized functionality. Team ID: UHG4J7F7NH App Apple ID: 67591326449 Thank you for your assistance. I am a student developer eager to start MVP testing as soon as this is resolved.

I paid my subscription from mobile but it's been more than a week and I haven't been able to make it work, I received the email confirmation and if I look at the subscriptions it is there but the developer.apple.com dashbards is asking me to pay again?

Hi there, I recently updated to the latest version of macOS Tahoe 26.3. Since then, Xcode is not able to resolve my Swift Package dependencies anymore. We use SSH for all our Github hosted packages. When package resolution is running, we randomly have Failed to verify SSH fingerprint on some remote package. Nothing has changed and it worked perfectly with Tahoe 26.2. The SSH have been reconfigured and known hosts have been verified. Is something changed between those 2 versions or is it a bug ?

Hello, I'm unable to kick off builds in Xcode Cloud today due to an error connecting to our SCM repo. "Repository Issue Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds." I can see that this is due to an HTTP 500 error on the /scm-repositories endpoint, which would normally indicate an issue in Xcode Cloud. If on the contrary this indicates an issue on my side, I'd like to hear details and what the resolution might be. Filed an issue here: FB22314855 (Xcode Cloud: HTTP 500 when connecting to SCM provider)

I'm based in Australia, and am having the following issue. After leaving this message I received another response from someone else who is also havign the same issue, I've pasted that too. I'm quite surprised to not see it mentioned, could be local to language settings or something. Here is the issue: Folk, I am having an issue where Xcode 26.3 with the new iOS26.2+26.3.1 Simulator update installed doesn’t render Unicode characters in the Canvas or in Simulator. They do render when running direct to a device. I’ve reset devices inside Simulator, cleared Derived Data, cleaned Build Folders etc but to no avail! Is anyone else seeing this, I can’t find a mention anywhere!! Thank you in advance. Yep. Same here. Can't see emojis on the emoji picker keyboard.

Hello everyone, I am looking for advice from anyone who has experience with Apple Developer account setup across countries. My Apple account is currently associated with the United States, but I live in Germany and would like my Apple Developer setup to be associated with Germany for tax and administrative reasons. At the moment, I have not enrolled yet in the Apple Developer Program, because I am hesitant to proceed while the account is still tied to the U.S. I want to avoid creating complications later around tax information, billing or account maintenance. My app is essentially ready, so I am trying to make the right decision before enrolling. I would really appreciate guidance on a few points: Has anyone enrolled first and then later changed the country association successfully? Is it better to update the Apple account to Germany before joining the Developer Program? For developers based in Germany, did Apple require anything specific for tax or identity verification? Would enrolling with the account still associated with the U.S. create problems later for App Store Connect, payments or tax forms? I contacted Apple Support on March 21st to clarify this, but I have not yet received a response, so I thought I would ask here in case others have gone through the same process. Any advice or shared experience would be very helpful. Thank you!

We're experiencing an issue where the CarPlay Simulator (from Apple Developer Additional Tools) stopped connecting to our iPhones as of March 4th, 2025. The simulator gets stuck indefinitely on "Connecting to phone" and never completes the pairing. Environment App: Oracle Field Service iOS app (with CarPlay support) Tool: CarPlay Simulator from Apple Developer Additional Tools (developer.apple.com/download/all/) Issue start date: Wednesday, March 4th, 2025 Tested on: Multiple Mac machines, multiple iPhones Multiple CarPlay Simulator versions tested What's happening The CarPlay Simulator launches but displays "Connecting to phone" indefinitely. It was working correctly prior to March 4th with no changes on our end. What still works CarPlay functions correctly when the same iPhone is connected to a real car, confirming the issue is specific to the simulator. Troubleshooting steps already attempted Reset permissions and re-added the simulator Forgot the simulator and re-paired it Changed the USB cable Tested on multiple Mac machines Tested on multiple iPhones Tried multiple versions of the CarPlay Simulator Confirmed no VPN is in use Confirmed with IT, no OS updates or enterprise restrictions were applied Questions Has anyone else experienced this since March 4th? Was there a change in CarPlay Simulator behavior or a requirement on the Apple side (certificate, entitlement, protocol) around that date? Is there a known workaround or fix?

Hello, I enrolled in the Apple Developer Program on March 22, 2026 and the payment has already been successfully charged. I also received an invoice the next day (March 23, 2026). However, my account is still not activated, and the system continues to prompt me to complete the enrollment or make the payment again. Is this a normal delay in activation? How long does it usually take for the account to be activated after payment? Do I need to take any additional steps, or should I contact support directly? Thank you for your assistance.