Hello, I’m using the latest version of Xcode, 26.6. I’m unable to permanently delete old installed iOS platform versions. I remove them from Xcode settings, and the deletion appears to complete successfully, but after rebooting my Mac they appear again, as if nothing had changed. Do you have any suggestions for how to remove them correctly and permanently?

Hi all, I have implemented a feature in my iOS application which checks the latest version available on App Store and if there is new update available it shows Pop to update the app. I am using this url for checki https://itunes.apple.com/lookup?bundleId= Issue: For some users this url returns old cached data which is previous version although new version is already live and i have verified this url directly via PostMan or other IDE.

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.

After updating to Xcode 26.5 Xcode crashes when I try to open my project. Directly before update everything was fine... Not using Beta-Software.. only stable versions What can I do? Will there be an update fixing this bug? `Application Specific Information: abort() called Application Specific Signatures: NSInternalInconsistencyException Application Specific Backtrace 0: 0 CoreFoundation 0x0000000186e711c0 __exceptionPreprocess + 176 1 DVTFoundation 0x000000010578a20c DVTFailureHintExceptionPreprocessor + 388 2 libobjc.A.dylib 0x00000001868fa91c objc_exception_throw + 88 3 Foundation 0x000000018868f498 -[NSFileWrapper regularFileContents] + 436 4 IDEStoreKitCore 0x000000030e002b20 $s15IDEStoreKitCore0aB13ConfigurationC4FileV17configurationData10Foundation0G0Vvg + 440 5 IDEStoreKitCore 0x000000030e001da0 $s15IDEStoreKitCore0aB13ConfigurationC13configuration3forACSo13NSFileWrapperC_tKFZ + 304 6 IDEStoreKitCore 0x000000030e003b0c $s15IDEStoreKitCore0aB13ConfigurationC13configuration2atAC10Foundation3URLV_tKFZ + 148 7 IDEStoreKitEditor 0x000000030e792ecc $s17IDEStoreKitEditor0aB20TextFragmentProviderC12generateSeed3for17completionHandlerySo11DVTFilePathC_ySo07IDETextefH0_pSg_s5Error_pSgtctFZ06$sSo27nefh28_pSgSo7NSErrorCSgIeyByy_ABs5o2_pR8Ieggg_TRAJSo0T0CSgIeyByy_Tf1ncn_nTf4ndg_n + 152 8 IDEStoreKitEditor 0x000000030e7922fc $s17IDEStoreKitEditor0aB20TextFragmentProviderC12generateSeed3for17completionHandlerySo11DVTFilePathC_ySo07IDETextefH0_pSg_s5Error_pSgtctFZTo + 52 9 IDEFoundation 0x000000010c922318 __113+[IDETextFragmentIndex runProvider:forFilePath:explicitFileDataType:initialTimestamp:priority:completionHandler:]_block_invoke + 204 10 DVTFoundation 0x00000001058a0638 __51-[DVTThrottledConcurrentQueue processQueueIfNeeded]_block_invoke + 80 11 DVTFoundation 0x0000000105892bd0 DVT_CALLING_CLIENT_BLOCK + 16 12 DVTFoundation 0x0000000105893548 __DVTDispatchAsync_block_invoke + 152 13 libdispatch.dylib 0x0000000186b8aa28 _dispatch_call_block_and_release + 32 14 libdispatch.dylib 0x0000000186ba44b0 _dispatch_client_callout + 16 15 libdispatch.dylib 0x0000000186b8f1c8 _dispatch_continuation_pop + 596 16 libdispatch.dylib 0x0000000186b8e844 _dispatch_async_redirect_invoke + 580 17 libdispatch.dylib 0x0000000186b9c980 _dispatch_root_queue_drain + 360 18 libdispatch.dylib 0x0000000186b9d120 _dispatch_worker_thread2 + 184 19 libsystem_pthread.dylib 0x0000000186d41e84 _pthread_wqthread + 232 20 libsystem_pthread.dylib 0x0000000186d40c10 start_wqthread + 8`

Hi Devs, I'm working with WatchOS for the first time and am having a frustrating time with Xcode to Watch, to say the least. I have a Series 9 dev watch and Xcode does not reliably connect to it. Spending 15-20 min per build/run attempt just trying to get xcode to find and connect to the watch. It WILL sometimes recognize and allow a build to run, the issue is I can't tell any reliable way to establish the connection. It drops after every build and leaves me at square zero. Current solution is some amount of force quitting, reconnecting iPhone to USBC, disconnecting watch to wifi and back on. Devices Window usually reads: Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters - swapping to some attempting to connect state that never (reliably resolves). Is this why no one builds for WatchOS? Hoping someone has pro tips on this.

I'm trying out Xcode 12 (beta) and encountered an issue with TextField when viewing it in a live Preview. Although the view is interactive (scrolling vertically seems to be OK) and a cursor appears in the TextField view when it is clicked on, keyboard input is ignored. The same code works as expected in Xcode 11.5. Simulator in both 11.5 and 12 exhibits expected behaviour. Is this a bug? I know there is an issue with interactivity in Preview with multiple views inside PreviewProvider but I'd assumed this is if you'd added multiple Views to the same body of this struct.

AI agentic coding is great, but it drifts away from the good practices and good code. Sometimes I am writing code while thinking what exactly to write, exploring the architecture solution, the data flow, not the technology, so making a prompt is not the best use case. I am doing iOS development in VSCode since preview version of Copilot launched, the auto-completions that AI provides IS the greatest tool a developer can have Please 🙏 prioritize the unimaginable good auto-completion that only Apple can provide, so that we can auto-complete function implementation, class implementation, multiple lines of comments in a fraction of a second

I have to say I'm extremely disappointed with Apple. For weeks, I've been trying to enroll as an individual in the Apple Developer Program, but every single attempt ends with the same message: "Your enrollment in the Apple Developer Program could not be completed at this time." I contacted Apple Developer Support, hoping they could explain the issue. Instead, I received this generic response: "For one or more reasons, your enrollment in the Apple Developer Program couldn't be completed. We can't continue with your enrollment at this time." No explanation. No guidance. No indication of what I did wrong or whether I can ever enroll. I sent additional emails asking for clarification, but they simply stopped responding. As an independent developer, this experience has been incredibly frustrating. I've spent countless hours building applications with the goal of releasing them on Apple's platform, only to discover that I can't even join the Developer Program—and no one is willing to tell me why. At this point, I honestly don't think developing for Apple is worth the time, effort, or investment. It's painful to realize how much work I've put into building apps that I may never be able to publish. This experience has completely changed my opinion of Apple. I'm so disappointed that I've decided to stop using Apple products altogether. I'll be moving away from my iPhone, Apple Watch, MacBook, and iPad because I no longer want to invest in an ecosystem that treats independent developers this way.

I know Xcode 27 is in beta but it appears that in Device Hub you can no longer drag and drop enterprise security certificates onto the simulators like you could in Xcode 26 (and earlier) simulators. I did put in a feedback request in (FB23369006) but I was wondering if anyone found a workaround. This hampers testing for enterprise users who don't have a physical device to test on.

Xcode 27 creates a placeholder for the bundle identifier of a new project. devplaceholder.$(PROJECT_UNIQUE_VALUE:identifier).$(PRODUCT_NAME:identifier) I have two questions. Is it enough to change the bundle id from the Signing & Capabilities panel or do we need to change it somewhere else? What are Apple recommendations? Should we only replace the devplaceholder value and keep the unique value and product name, provide our won id but keep the product name, or replace everything with our own bundle ID? Thanks

After adding the Mockable package to a project that already used swift-dependencies and updating to Xcode 26.6, my release/archive builds got ~2 min slower because swift-syntax was being recompiled from source every time. Thorougly investigating and fixing this took about 3 hours and I thought I'd share my findings for the next person encountering such an issue: Findings: I confirmed the prebuilt swift-syntax is used for swift-syntax 603.0.2 in Xcode 26.6 when building a package separately (I suspect dependencies to older versions might cause issues, but didn't fully investigate this) It can be checked if the prebuilt version of swift-syntax is used via the build log. If working correctly/using the prebuild version, swift-syntax isn't mentioned at all. One package resolved to swift-syntax 600.x, this would trigger a build of swift-syntax. After updating the dependencies it worked fine. Even if the version in the xcodeproj resolves to a confirmed-working version of swift-syntax, it seems other packages might trigger the swift-syntax build under the hood. Opened the packages individually and built separately with Build for » Profiling to investigate. In my case, another issue was triggering the problem: The swift-snapshot-testing open source package declared a swift-syntax dependency although it didn't actually use it. That caused swift-syntax being built (not sure why, maybe Xcode thinks it's a non-macro usage of swift-syntax?) Creating a fork of the package and removing the dependency fixed the issue. After both fixes, in the full project, a Product → Clean Build Folder + restart Xcode was required before swift-syntax stopped being rebuilt. See also: Xcode 26 Release Notes — Swift Macros Build Performance:

Hello, I am posting here as a last resort because I have been unable to get any assistance through Apple Developer Support. Case ID: 102888399005 Timeline: I started the Apple Developer Program enrollment process using the Apple Developer app on my iPhone. I successfully uploaded my ID document. After that, I received a message stating that my identity could not be verified. I submitted a support request to Apple Developer Support. I received a reply from Developer Support, but the response did not address my issue or provide any guidance on how to continue the enrollment process. The status in the Apple Developer app on my iPhone later changed to "ID Verification Rejected". I replied to the existing support case and, after receiving no response for two weeks, submitted a new support request. Several weeks have now passed without any response to either request. The enrollment page on the web now displays the message: "Your enrollment could not be completed." The Apple Developer app for iOS still shows "ID Verification Rejected" In the Apple Developer app for macOS, I am able to start the enrollment process. However, after scanning my ID document, the app either displays a completely black image or crashes immediately. At this point, I have multiple open support requests and an unresolved case, but I have not received any guidance on why my identity verification was rejected or how I can proceed with enrollment. I would greatly appreciate any assistance, guidance, or help in getting this case reviewed by the appropriate team. Thank you for your time. Best regards, Jan Bula

Environment: macOS 26.5.1 (Build 25F80) Xcode 26.6 (Build 17F113) iOS 26.5 Simulator Runtime (Build 23F77) Device: Apple Silicon (arm64) Summary: The iOS 26.5 simulator fails to boot with NSPOSIXErrorDomain Code 4 (Interrupted system call). The underlying error indicates launchd_sim cannot bind to its session, suggesting the CoreSimulator session management is broken in this macOS + Xcode + runtime combination. Steps to Reproduce: Install macOS 26.5.1 and Xcode 26.6 Open Simulator.app or run xcrun simctl boot Attempt to boot any iOS 26.5 simulator device Expected Result: Simulator boots successfully and reaches the Booted state. Actual Result: Unable to boot the Simulator. Domain: NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding Domain: com.apple.SimLaunchHostService.RequestError Code: 4 Workaround: Installing an older stable iOS simulator runtime (iOS 17.x or 18.x) and targeting that instead allows simulators to boot normally. Additional Notes: Issue persists after full Mac restart xcrun simctl erase all and xcrun simctl delete all do not resolve it The iOS 26.5 Simulator volume mounts correctly at /Library/Developer/CoreSimulator/Volumes/iOS_23F77 launchd_sim binary is present and properly code-signed

When I try to enroll Apple Developer Program for a company, getting an error. "We are unable to process your request. An unknown error occurred." Please, help me. What am i doing wrong?

Hello, I am trying to enroll in the Apple Developer Program, but I keep receiving this error: "Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time." I have already tried using different Apple ID accounts, different devices, different browsers, clearing cache/cookies, and different internet connections, but the error still appears. Could you please tell me what is causing this issue and how I can fix it? If needed, I can provide any required documents or verification information. Thank you.

Hi Has anybody had problems setting up a Developer account and setting their location as Guernsey, Channel Islands? I have spent a couple of months developing an app but when I went to create my Developer account Apple won’t accept my Drivers License ID. I have contacted them but for over a month I just get stock answers like this each time I contact them. ”Thank you for your interest in the Apple Developer Program. This is Vivian, senior Advisor with Developer Support. I hope this message finds you well. We're currently reviewing your inquiry and will reply to you as soon as an update is available. “

👋🏻 Hello Apple Developer Community, I’ve recently got the problem with the current Xcode Beta Version and the Preview Feature. Because when I try to load the Preview, the RAM Usage spikes and it’s nearly at the limit on my MacBook (16GB RAM). (Note: This is happening while loading up the Preview) But when I haven’t loaded the Preview Window, the overall RAM Usage of my system is ver low (Note: This is when Xcode has is not loading the Preview) (Note: This is after quitting Xcode for cancelling the load of the Preview) All Pictures are in German, sorry for that ☹️. What are possible problems or solutions against this problem? Have a nice day / evening 😁

Hi,My itunes connect keeps telling me that I need to accept the updated license agreement and review the new paid applications schedule. When I go to my developer account, I don't see anywhere that I can accept any agreement. When I go to Agreements, taxes, and banking in itunes connect I don't see anything that can be done there either. I am the only user on my account.Please help 😟

I’m having an issue with the Apple Developer Program. I received a notification that the Apple Developer Program License Agreement has been updated and must be accepted in order to continue submitting and updating apps. The problem is that after signing in to my Apple Developer account, I don’t see any option to accept the new agreement. Instead, I’m shown a “Join the Apple Developer Program” screen, as if I’m not enrolled in the program, even though I have active apps on the App Store. In App Store Connect, I can see the agreement status as “Active (New Agreement Available)”, but there is no visible way to actually review or accept the updated version. Has anyone experienced a similar issue and knows how to fix it?

I added a workflow and it seemed to work fine so lets add them all ! I added a second workflow and it seems to see the repository but not the branches in the repository. I have googled and even asked AI. Checked and it's installed with all repo access on Github Removing the repo .. adding it back Deleting the workflow and adding it back Adding the workflow from the browser Adding the workflow from XCode Nothing seems to work, but the first one I created works. Is there paid support for Xcode Cloud ? I s there a version control that works better with Xcode Cloud? Any suggestions are appreciated.