When I archive and distribute any iOS app from Xcode 27.0 RC on macOS 27.0 Golden Gate, the upload stalls indefinitely at “Preparing to upload [App].ipa”. The archive, signing, provisioning, IPA packaging, and App Store Connect authentication all complete successfully. This is reproducible with multiple unrelated iOS projects on the same machine, so it does not appear to be caused by a specific app, signing configuration, asset, or bundle identifier. Cancelling the upload is the only way to exit the stalled state. I also checked with ChatGPT Codex if it can narrow down the issue. It states: "The failure occurs when Xcode launches the swinfo utility from the ContentDelivery framework to generate the asset description.swinfo crashes with SIGSEGV / exit code 139. The crash report reports:Thread stack size exceeded due to excessive recursion". But I actually never got an error message during the upload itself, it just hangs indefinitely at "preparing to upload..." (Tried it several times up to 36h). This issue is new since I updated to macOS Golden Gate and xCode 27 RC. Xcode Cloud is the only working option right now to upload a Build to App Store Connect. Anyone experiencing the same issue and found a solution? What I already tried: Revoke and renewed my Apple Distribution certificate. Delete xCode, Installed it again (I also installed xCode 27.2 Beta which I knew would not work to upload an app to App Store Connect from a Beta version). Created a brand new project and tried to upload this. Also hang at "preparing to upload..."

I like to use Window Tabs, setting them up with appropriate panels when working on SwiftUI views, writing tests, etc. Many times now, I open a project in Xcode only to discover the main window is very small, what was expanded in the project outline is incorrect, and the window tab bar is hidden. Showing the window tab bar then just shows a single empty tab named "New Editor". Since I didn't add any new files today or change project settings (nothing would have changed the .xcodeproj package of files), I restored a backup and that opened up a-ok. Though I first saved the bad project. In analyzing differences between the two .xcoeproj files, I can only imagine this an issue with UserInterfaceState.xcuserstate. Though it's not practical at all to see what the changes are due to different ordering. I did notice that the bad .xcodeproj version had a massive Base64 encoded block for some IDENavigatorModeSolitary entry. The working project had a much smaller encoded block. Anyone else run into this? For those that are now using the new JSON project files, has this still been an issue?

The iOS 17 simulator does not respond at all when I try to interact with it. The simulator is not frozen as I can still control appearance and launch apps via the right sidebar. Things like the home button and clicking on the screen simply don’t work. I am using Xcode 27 beta 6. Feedback ID: FB24674634

M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible Background This is a follow up to my November 2024 thread "Keychain issues after installing backup on new Mac" which was closed because I had a temporary workaround. That workaround using my wife's MacBook Air for signing is not sustainable. I used AI assistance to determine the root cause. My DTS case 102877839447 is open but has not yet been forwarded to a DTS engineer. Environment Mac Mini M4, macOS 15.4.1 (Build 25E253) Xcode 26.4.1 (17E202) Team ID: Q23726668V (Computerade Products) Working comparison machine: MacBook Air, macOS 15.3 Precise Bug — Reproducible Every Time Every time Xcode generates a new certificate and key pair on my Mac Mini: Certificate: Apple Development: Michael Birch (9KD5TCGGHG) ✅ Private key: Apple Development: Michael Birch (Computerade Products) ❌ The key uses the organization name instead of the certificate identifier. They never pair as a valid codesigning identity. security find-identity -v -p codesigning always returns 0 valid identities. Cryptographic Evidence The internal application labels confirm the keys are cryptographically unrelated to their certificates: Key internal application label: 53C26EB056997276B5E938258D00665ACABD1F0F Certificate public key hash: 57cd1af4a9162f26b1a6d750e05a63a2166b75ff These do not match ❌ Confirmed Eliminated As Causes Keychain search list corruption — found and fixed Partition list — set correctly Access control — set to allow all applications Full Disk Access — granted to Xcode Xcode caches and preferences — completely cleared Login keychain — completely reset Orphaned certificates and keys — all removed SIP enabled, system fully up to date Valid P12 Import Also Fails A p12 exported from the working MacBook Air and cryptographically verified as a matched pair also fails on the Mac Mini: security import returns MAC verification failed Keychain Access import returns OSStatus -2 Importing certificate and key separately as PEM files succeeds but they are not recognized as a valid identity pair despite matching application labels A3F3F193B7896DA9055353F59AB450778CB09AE7 Question Is there a known issue with M4 Mac Mini keychain infrastructure where private keys are generated with incorrect internal application labels? Is there a lower level diagnostic or fix beyond what the security command provides? The problem is specific to my Mac Mini M4 and persisted thru more than a year of Mac OS and xCode updates.

I have tried many times to purchase the apple developer account but it always give me the error that this product is not available in your region country I always tried to make that purchase complete but got disapointed just because of error. first they put me on hold for hours an hours then they don't entertain us although I am a genuine user of apple and we are a registered entity. so please give a look on it .

Hi Team, My Mac has already been upgraded to macOS 27 and currently has Xcode 27 installed. However, I have a development requirement to use Xcode 26.5 as well. Is there any supported way or workaround to install and run Xcode 26.5 on macOS 27? If it is not supported directly, what would be the recommended approach to use Xcode 26.5? Thanks, Reshma

I have been developing an iOS app I have been wanting to release. In the past, I have been able to use my apple account to put things to various testing builds. I did not realize my account had expired earlier this year and I had a build I wanted to work. When I renewed my account, it said it would take a week to activate. It is now over that week period and I cannot use my developer account properly still. Xcode says I do not have a valid method to upload my new build and all my old builds for some reason cannot be used. My account has a red 'x' next to it when I try to manage it on my macbook. Does anyone have any advice on how to help as I have 2 have emails to apple support over the past week that have just been ignored.

Hello, I am unable to complete my Apple Developer Program enrollment. My identity verification has already been completed, and I was able to submit the membership purchase. I received the Order Acknowledgement from Apple, but the payment is never processed and the membership is not activated. I contacted my bank in Kyrgyzstan. They confirmed that the card is active, there are no restrictions on it, and, most importantly, they have received no authorization attempt from Apple at all. I have already contacted Apple Developer Support: Case ID: 102968515655 Unfortunately, I have not received a resolution or further instructions. My situation: Individual enrollment Identity verified with a Russian passport Payment card issued by a bank in Kyrgyzstan Order Acknowledgement received No charge or authorization attempt reaches the bank Developer Program membership remains inactive Could Apple Developer Support please check whether my enrollment/payment is stuck on Apple's side and advise how I can complete the existing enrollment? If necessary, could the enrollment/payment state be reset so that I can submit the purchase again through the supported method? Thank you.

Hello I cannot seem to get past the final step in pairing my Ultra Watch 3 to Xcode 27 RC1.. I have tried this on a Mac Mini M4 and a Mac M1.. Both Macs are running 26.6.2 In both cases, XCode seems my iPhone and I am able to deploy to that physical iPhone. I have my iPhone connected via a USB cable. When going into Developer Mode on the watch and then opening up the "Pair Nearby Device" in Device Hub, I can see either my M1 or my M4 (depending on which one is trying to connect), I can select it, it asks for a pass code and then asks me to pair. When I do, it simply returns back to the previous screen asking if I'd like to pair again.. Any ideas ?

Hi Kurdish sorani keyboard on IOS 27 it’s ver bad And when writing some Word and doing space between any word keyboard change for number and -/:(()£&@“.,?!’ On IOS 25 and 26 very good and perfect. and we need add Kurdish language Sorani add to translate thank you

Hello Apple Developer Community, I’m trying to connect a Bitbucket repository to Xcode Cloud through App Store Connect, but the connection consistently fails with an HTTP 403 response. Environment Product: Xcode Cloud / App Store Connect SCM: Bitbucket Cloud Integration: App Store Connect → Xcode Cloud → Bitbucket Date: September 15, 2026 Time: 3:51:44 PM IST / 10:21:44 UTC Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E HTTP Status: 403 I have Administrator access in both App Store Connect/Apple Developer and the Bitbucket workspace/repository. What I have already checked I contacted Bitbucket Support and provided them with the browser network/HAR capture from the failed connection. Bitbucket confirmed that the App Store Connect Bitbucket callback returned HTTP 403. However, they explained that the browser capture cannot show the subsequent server-to-server communication between Apple/Xcode Cloud and Bitbucket. Bitbucket therefore asked Apple to investigate the server-side request using the Apple Correlation ID and timestamp. They indicated that the failure could potentially involve: Apple rejecting the Bitbucket OAuth callback. Apple receiving the callback but failing while processing it. A server-to-server request from Apple to Bitbucket returning an error. An OAuth authorization-code or access-token exchange failure. The 403 being generated by Apple's callback service. My question Has anyone experienced a similar HTTP 403 when connecting Bitbucket Cloud to Xcode Cloud through App Store Connect? Also, is there a known Xcode Cloud/App Store Connect requirement for Bitbucket OAuth or access tokens that could cause this type of 403 even when the user has administrator permissions? If an Apple engineer is able to review the server-side logs, could the following details help identify the failure? Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E Timestamp: September 15, 2026, 10:21:44 UTC HTTP Status: 403 Bitbucket has already confirmed that the relevant server-to-server communication is not visible in the browser HAR, so I’m trying to determine which side is generating the 403 and at which stage of the OAuth flow it occurs. Any guidance from someone familiar with Xcode Cloud + Bitbucket integration would be greatly appreciated. Thank you.

Hello all, Yesterday, I found out that there's 60GB's of old simulator volumes on my mac in /Library/Developer/CoreSimulator/Volumes/. When I try to delete those through Xcode Settings -> Components under Other Installed Platforms, it looks like they are deleted, but after restarting my Mac, they simply return. I tried the solution proposed here (which is to delete the dmg files in /Library/Developer/CoreSimulator/Images/), but in my case, there are no dmg files in there. So it looks like they were properly deleted, unlike those in /Library/Developer/CoreSimulator/Volumes/. I could obviously try to delete the dmg files in /Library/Developer/CoreSimulator/Volumes/, but that doesn't work according to a post on reddit that I'm not allowed to show here (It's called 'Deleted 240GB of Xcode simulators multiple times but they keep remounting - how do I permanently remove them?') And I wonder if it's a safe thing to do. Do you have any suggestions for how to remove the old volumes correctly and permanently?

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.

Environment: Xcode 27 (macOS 27.0, build 26A428) iOS 27.0 simulator (build 24A434), tested on iPhone 18 Pro CoreSimulator 1174.9.2 Large app target: dozens of linked frameworks (first-party SPM modules plus several third-party SDKs) it occurred on xcode 26 also Description: SwiftUI canvas previews consistently crash XCPreviewAgent with EXC_BAD_ACCESS / SIGSEGV when rendering previews for a fairly large app target, across multiple different SwiftUI views (not tied to one specific file's code). Workaround found: the crash does not occur when "Use Legacy Preview Execution" is enabled (Xcode's preview settings). With the default (non-legacy, JIT-based) preview execution path, it crashes reliably; switching to legacy execution, previews render normally. Possible contributing factor — project size / timing: we suspect the size of the project may also be a factor, independent of the crash itself. The new (non-legacy) execution path recompiles/JITs the app for the canvas on every preview, and for a target this large that process takes noticeably longer than it does under legacy execution. It's plausible that on top of the crash described below, the new path is also more prone to timing out or failing under load on larger projects, simply because there's more to JIT-compile and load within whatever time budget the preview agent allows. We can't fully separate "crashes because of X" from "runs out of time because of project size" from the crash logs alone, but both seem worth flagging since they may share the same root cause in the new execution path's handling of larger binaries. Crash signature #1 (default preview execution, first attempts): Crashing Thread: 0 libswiftCore.dylib swift_conformsToProtocolMaybeInstantiateSuperclasses(...) 1 libswiftCore.dylib swift_conformsToProtocolWithExecutionContext 2 libswiftCore.dylib swift::_conformsToProtocol(...) 3 libswiftCore.dylib swift::_checkGenericRequirements(...) Termination: SIGSEGV / Segmentation fault: 11 Crash signature #2 (default preview execution, after removing an unrelated third-party SDK dependency from the previewed module, to rule it out as a cause): Crashing Thread ("com.apple.xojit_executor.wrapper_functions"): 0 libobjc.A.dylib readClass(objc_class*, bool, bool) 1 libobjc.A.dylib map_images_nolock 2 libobjc.A.dylib map_images 3 libobjc.A.dylib _objc_map_images 4-7 <unsymbolicated / anonymous image, source="A" (Absent) in the crash report> Exception: EXC_BAD_ACCESS (SIGSEGV), KERN_INVALID_ADDRESS In the second case, the crash log's usedImages list shows the frames above the objc runtime resolving to an image with no path, no resolvable UUID, and "source": "A" — this appears to be the dynamically JIT-compiled preview binary that XOJITExecutor builds and hot-loads for the canvas (rather than a normal on-disk framework), and the crash occurs while the Objective-C runtime is registering classes from it during _objc_map_images. What we've ruled out: Not caused by the specific SwiftUI view being previewed — reproduces across multiple unrelated views in the same target. Not caused by a specific third-party SDK: we removed a heavyweight closed-source analytics SDK dependency from the previewed module entirely (confirmed via successful xcodebuild build with zero references left), and the crash still occurred with an equivalent signature under default preview execution. Confirmed via symbolicated .ips crash reports in ~/Library/Logs/DiagnosticReports/XCPreviewAgent-*.ips that the crashing frames are inside Apple's own preview infrastructure (libobjc.A.dylib, libswiftCore.dylib, XOJITExecutor), not in application or third-party framework code. Confirmed the failure is specific to the new (non-legacy) preview execution path: enabling "Use Legacy Preview Execution" eliminates the crash entirely, with no other changes. Question for the community: Has anyone else seen SwiftUI Previews crash with a libobjc/map_images or swift_conformsToProtocol* segfault specifically on Xcode 27 / iOS 27 simulator with the new (non-legacy) preview execution path, for apps with a large number of linked frameworks? Does project size/build time make the new execution path more likely to fail or time out for anyone else? Is "Use Legacy Preview Execution" the recommended workaround until this is fixed, or should this be filed separately as Feedback?

For the life of me, I cannot find how to bring up the Siri Remote in the Apple TV Simulator in Xcode 27 Device Hub (Beta). Is it no longer available? I have always seem to have had issues using the computer's keyboard for navigating my tvOS apps. Maybe it's me, but the Siri Remote always worked perfectly fine. I hope the remote will make a reappearance in the next beta... ?

I have been trying to complete my enrollment with Apple Developer for 6 weeks now. Review of my business documents was finally completed on Sept 10, but payment hasn't been processed. Does anyone have any feedback on how to complete payment or get in contact with the developer team? I tried calling the call center but they instructed me to create a ticket, which I did, but there's been no response

Xcode 27 keeps failing to download the Documentation, it shows "Preparing to download" and spins the camomile endlessly. I checked logs (with help of AI) and found this: Xcode queries com.apple.MobileAsset.AppleDeveloperDocumentation. Metadata catalog loading suceeds. Then asset resolution loops with: MAQueryTooManyResults - Asset load result ... 13 (MAQueryTooManyResults) Also CSSMERR_CSP_VERIFY_FAILED from mobileassetd during this sequence. In my /System/Library/AssetsV2 I have 3 old .asset files all from Xcode 26, the last one updated on Jun 12. But I don't think it's the reason for the error. What would you suggest to recover the documentation?

Hello, I noticed that iPhone 18 series devices are missing from DeveloperDiskImages in Xcode 27.1 beta 1. I checked /Library/Developer/DeveloperDiskImages/iOS_DDI/Restore/BuildManifest.plist and found no entries for iPhone 19,x in SupportedProductTypes. Could this be due to downloading the wrong version of Xcode, or is there another reason? Latest iPhone type is iPhone18,5, here is the content of BuildManifest.plist from Xcode 27.1 beta 1: <key>ManifestVersion</key> <integer>0</integer> <key>ProductBuildVersion</key> <string>27A9269</string> <key>ProductVersion</key> <string>1.0</string> <key>SupportedProductTypes</key> <array> <string>ComputeModule13,1</string> <string>ComputeModule13,3</string> <string>ComputeModule14,2</string> <string>Mac14,14</string> <string>iPad11,1</string> <string>iPad11,2</string> <string>iPad11,3</string> <string>iPad11,4</string> <string>iPad11,6</string> <string>iPad11,7</string> <string>iPad12,1</string> <string>iPad12,2</string> <string>iPad13,1</string> <string>iPad13,10</string> <string>iPad13,11</string> <string>iPad13,16</string> <string>iPad13,17</string> <string>iPad13,18</string> <string>iPad13,19</string> <string>iPad13,2</string> <string>iPad13,4</string> <string>iPad13,5</string> <string>iPad13,6</string> <string>iPad13,7</string> <string>iPad13,8</string> <string>iPad13,9</string> <string>iPad14,1</string> <string>iPad14,10</string> <string>iPad14,11</string> <string>iPad14,2</string> <string>iPad14,3</string> <string>iPad14,4</string> <string>iPad14,5</string> <string>iPad14,6</string> <string>iPad14,8</string> <string>iPad14,9</string> <string>iPad15,3</string> <string>iPad15,4</string> <string>iPad15,5</string> <string>iPad15,6</string> <string>iPad15,7</string> <string>iPad15,8</string> <string>iPad16,1</string> <string>iPad16,10</string> <string>iPad16,11</string> <string>iPad16,2</string> <string>iPad16,3</string> <string>iPad16,4</string> <string>iPad16,5</string> <string>iPad16,6</string> <string>iPad16,8</string> <string>iPad16,9</string> <string>iPad17,1</string> <string>iPad17,2</string> <string>iPad17,3</string> <string>iPad17,4</string> <string>iPad5,1</string> <string>iPad5,2</string> <string>iPad5,3</string> <string>iPad5,4</string> <string>iPad6,11</string> <string>iPad6,12</string> <string>iPad6,3</string> <string>iPad6,4</string> <string>iPad6,7</string> <string>iPad6,8</string> <string>iPad7,1</string> <string>iPad7,11</string> <string>iPad7,12</string> <string>iPad7,2</string> <string>iPad7,3</string> <string>iPad7,4</string> <string>iPad7,5</string> <string>iPad7,6</string> <string>iPad8,1</string> <string>iPad8,10</string> <string>iPad8,11</string> <string>iPad8,12</string> <string>iPad8,2</string> <string>iPad8,3</string> <string>iPad8,4</string> <string>iPad8,5</string> <string>iPad8,6</string> <string>iPad8,7</string> <string>iPad8,8</string> <string>iPad8,9</string> <string>iPhone10,1</string> <string>iPhone10,2</string> <string>iPhone10,3</string> <string>iPhone10,4</string> <string>iPhone10,5</string> <string>iPhone10,6</string> <string>iPhone11,2</string> <string>iPhone11,4</string> <string>iPhone11,6</string> <string>iPhone11,8</string> <string>iPhone12,1</string> <string>iPhone12,3</string> <string>iPhone12,5</string> <string>iPhone12,8</string> <string>iPhone13,1</string> <string>iPhone13,2</string> <string>iPhone13,3</string> <string>iPhone13,4</string> <string>iPhone14,2</string> <string>iPhone14,3</string> <string>iPhone14,4</string> <string>iPhone14,5</string> <string>iPhone14,6</string> <string>iPhone14,7</string> <string>iPhone14,8</string> <string>iPhone15,2</string> <string>iPhone15,3</string> <string>iPhone15,4</string> <string>iPhone15,5</string> <string>iPhone16,1</string> <string>iPhone16,2</string> <string>iPhone17,1</string> <string>iPhone17,2</string> <string>iPhone17,3</string> <string>iPhone17,4</string> <string>iPhone17,5</string> <string>iPhone18,1</string> <string>iPhone18,2</string> <string>iPhone18,3</string> <string>iPhone18,4</string> <string>iPhone18,5</string> <string>iPhone8,1</string> <string>iPhone8,2</string> <string>iPhone8,4</string> <string>iPhone9,1</string> <string>iPhone9,2</string> <string>iPhone9,3</string> <string>iPhone9,4</string> <string>iPod9,1</string> <string>iSim1,1</string> </array>

I am unable to debug an iOS 27 device using Xcode 26. I can not currently update Xcode so I'm stuck with it for the time being. There used to be the hack where you could copy the newer /Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport into the older Xcode, but that path doesn't exist in Xcode 27. Is there any way to debug an iOS 27 device using Xcode 26? Currently I see "Insufficient metadata to manage symbols" in Devices & Simulators for that connected device.

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.