For the last 2 months I have been submitting the first iOS builds of my app “Zema Kirar”. However Appstore connect wrongly rejects it claiming it was built bu a BETA version of xcode and / or MacOS. My Dev Environment I am Running macOS Tahoe 26.6.2, and Xcode 26.6 (Build 17F113). Both are the ”current” latest public (GM) versions required by apple. Steps to reproduce: Xcode cloud build/ and transporter upload completes > I select the build > click save > click on Submit. Appstore connect shows error: Unable to add for Review. The items below are required to start the review process: New apps and app updates must be built with the latest public (GM) versions of Xcode, and the iOS, macOS, watchOS, and tvOS SDK. Apps built with the beta versions aren’t allowed.

Xcode 26.5 stucks on Localization Generating Comments: Running on macOS Tahoe 26.5 When this happens, Xcode does not add new keys, although enabled: The only (known) workaround is to restart Xcode. Same happened with Xcode 26.4, 26.4.1 on macOS 26.4.1.

Is anyone else using one of the "Dark" editor themes (such as "Default (Dark)" or "Classic (Dark)" in Xcode? And is anyone doing this with Xcode 26 on macOS 26? Here's the result while using the "Default (Dark)" theme while my Mac is in "light" mode: Note that the black background of the editor goes all the way to the far left edge of the Xcode window. The large gray area in the project tree is the black background bleeding through the sidebar. This is really distracting. Is there a way to fix this (besides not using a dark theme - I've been using dark themes for over 30 years)? This appears to be a poor design decision in macOS 26 to have split views show the background of the secondary column behind the primary column. iPadOS 26 has the same issue (see https://developer.apple.com/forums/thread/800073).

I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators. Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app. Issue A (when Watch is visible in Xcode) In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect. Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.” In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation. Issue B (after unpairing Watch in Xcode only) I unpaired/removed the Watch in Xcode (Devices & Simulators). I did not unpair the Watch from the iPhone. Now: iPhone appears in Xcode and works normally for builds. Watch is still paired to the iPhone and works normally. Watch no longer appears anywhere in Xcode Devices & Simulators (no paired watch section, no watch run destination). What I’ve tried Reboots of Mac, iPhone, Watch (multiple times) Watch unlocked, awake; iPhone unlocked and close to Watch Verified Watch is paired and connected in iPhone Watch app Developer Mode enabled on iPhone and Watch Wi-Fi and Bluetooth ON (Mac/iPhone/Watch), tried toggling both Tried on home Wi-Fi and also with iPhone hotspot (same result) Resetting trust prompts / reconnecting iPhone via USB, re-trusting Mac Apple Watch: “Clear Trusted Computers” Xcode: removing/re-adding devices; clearing derived data; restarting Xcode Watch Developer networking test: Responsiveness = Medium (430 RPM) Questions 1. Is this a known issue/regression with Xcode 26.2 + watchOS 26.2 tunneling (CoreDevice / devicectl)? 2. Is there an Apple-supported way to force Xcode to re-discover a paired Watch after it was removed from Xcode Devices & Simulators (without unpairing the Watch from the iPhone)? 3. Any recommended logs or diagnostic steps I should collect (Console logs, sysdiagnose, specific Xcode/CoreDevice logs) to include in a Feedback report? If helpful, I can provide the full error text from Xcode’s Devices window and any logs you recommend. Thank you in advance,

Installing a development build on a physical iPhone fails with: 0xE8008018 - The identity used to sign the executable is no longer valid. On the same Mac, same iPhone, same codebase and same Xcode, switching to a free personal Apple ID team installs and runs with no error. Only builds signed with our paid organisation team fail. Nothing else changes between the two runs. We have already regenerated certificates and provisioning profiles, deleted the profiles folder, cleared DerivedData, removed old identities from the keychain, trusted the profile on device, and tried both automatic and manual signing. None of it changes the result. We have also gone through the existing threads on this error and none of the suggested fixes apply. The build validates locally but the device rejects the identity. Since the signing team is the only variable between success and failure, what should we be looking at? A support case is open with Developer Support but we have not had a technical response yet.

If you're on an Intel Mac, here's the reason and the fix. Cost me an evening, and I found nothing online except closed bug reports with the same symptom. The problem: The browser flow works fine. You authorize, the page confirms, Xcode acts like nothing happened, no error anywhere. Xcode only downloads the Apple Silicon (arm64) build of its agent binaries. On Intel they can't run at all. The process meant to receive your login dies instantly with "bad CPU type in executable" and Xcode never surfaces it. Check if this is you: file ~/Library/Developer/Xcode/CodingAssistant/Agents/claude/*/claude If it says arm64 and your Mac is Intel, that's the problem. The fix: Open the Info.plist next to the binary. It has the exact download URL. Download the x64 build of the same version. → Claude: change darwin-arm64 to darwin-x64 in that URL. → Codex: grab codex-x86_64-apple-darwin.tar.gz from the matching rust-v release on GitHub. Replace the binary and make it executable: chmod 755 Update the checksum in Info.plist. It's a plain SHA-512: shasum -a 512 Restart Xcode and sign in again. Bonus (Claude Pro / Max) Run claude setup-token in Terminal, then add the token to: ~/Library/Developer/Xcode/CodingAssistant/ClaudeAgentConfig/settings.json {"env": {"CLAUDE_CODE_OAUTH_TOKEN": "your-token"}} Pick "Authenticate with Configuration File" in the agent menu. Runs on your subscription no API key. Heads up: an Xcode update can re-download the wrong binary, so you may have to repeat this until Apple fixes the architecture detection.

I'm unable to use the Claude Agent in Xcode 26 (stable release) running on macOS 27 beta 5. Steps to reproduce: Open Xcode 26 Settings > Intelligence Select Claude Agent Expected: The Account section loads and allows me to sign in / manage my Claude account. Actual: The Account row shows a loading spinner indefinitely and never resolves, so I can't sign in or use the Claude Agent at all. Environment: Xcode 26 (stable), macOS 27 beta 5. Is this a known incompatibility with macOS 27 beta 5? Is there a workaround (e.g. clearing a cache or re-adding the account) to get the Claude Agent account section to load?

I use a free Apple Personal Team with Xcode for on-device testing. My Apple Development certificate created on 15 August 2026 shows “Missing Private Key”, and Xcode is not allowing me to create a fresh replacement certificate. I have already contacted Apple Developer Program Support, and they directed me to the Apple Developer Forums for technical assistance. How can I revoke/reset the unusable certificate or clear the certificate state for my Personal Team so that Xcode can create a new Apple Development certificate?

Hi Apple Developer Community, I’m experiencing a significant delay with my first app submission and wanted to check if anyone else is facing the same issue. I submitted my app Vetline (iOS 1.0) for App Review on August 10, 2026 at 6:55 PM. As of today, August 20, the status is still: Waiting for Review I have not received any communication from App Review or any request for additional information in the Resolution Center. I also contacted Apple Developer Support regarding the delay, but so far I have only received an acknowledgment that my query was received and no further update. Has anyone submitted an app around August 8–12 and experienced a similar delay? If so, how long did it take before your app moved from Waiting for Review to In Review? I’d really appreciate hearing from other developers who are currently experiencing this. Thanks!

I tried to upload my build into testflight with XCode -> Product -> Archive -> Distribute App but this error keeps showing up: "No Team Found in Archive, Use the Signing & Capabilities editor to assign a team to the targets and build a new archive." However, my Apple ID IS connected and the bundle ID is the same as in my App Store Connect. What can I do? I tried deleting all archives, restarting Xcode & my Mac, still nothing happend. I can't get it to upload...

I've been trying to submit a new software update. But App Store Connect doesn't show the last Build I uploaded with Xcode's Organizer. It's been 30+ minutes. Yet, System Status doesn't indicate an outage. What's the point of their having this site? Or is it just I who is having trouble?

I constantly manually allow Codex to read Xcode 27 skills, but I don't want to allow it to read from any arbitrary directory, so I didn't enable always allow AgentRead. Question is in the title

MacBook Air (Apple silicon), macOS 26.6.2 (25G83). I have a persistent CoreSimulator/MobileAsset issue. I do not have an Xcode project, Simulator devices, or an active need for iOS Simulator runtimes. Using Apple’s signed CoreSimulator simctl binary, I removed iOS 18.4 (22E238) and iOS 18.5 (22F77) through the documented: simctl runtime delete workflow, after simctl reported each runtime as Ready, Verified, and Deletable. Immediately after deletion, the runtime registration and mounted runtime image disappeared. However, after a normal Mac restart or later CoreSimulator service activity, both runtimes reappear under new image UUIDs and are automatically mounted read-only again. The underlying Apple MobileAsset parents remain present and report NeverCollected: iOS 18.4 / build 22E238: about 8.9 GiB iOS 18.5 / build 22F77: about 8.9 GiB The related CoreSimulator dyld cache also rebuilds to about 7.1 GiB. I have not manually deleted protected Apple assets, killed Apple services, or modified mounts. The only removal attempted was Apple’s own simctl runtime delete command. Expected result: After a successful documented runtime deletion, the runtime should remain unregistered and unmounted, and the Apple-managed backing storage/cache should become reclaimable through a supported process. Observed result: The same runtime builds return after restart/service activity, with new UUIDs and automatic mounts, while their retained MobileAssets remain. Could Apple please advise why CoreSimulator/MobileAsset reconciliation is re-registering deleted runtimes, whether NeverCollected prevents supported cleanup, and what supported procedure can permanently remove or reconcile these unused runtimes? Useful read-only checks: SIMCTL_PATH=/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/Resources/bin/simctl "$SIMCTL_PATH" list runtimes "$SIMCTL_PATH" runtime list -v du -skx /Library/Developer/CoreSimulator/Caches/dyld

Hi everyone, I’m currently running macOS 27.0 beta (26A5388g) on my Mac, along with the latest Xcode 27 beta, and I’ve recently started experiencing a serious issue where multiple macOS system services are repeatedly crashing. Initially, I started getting repeated “intelligencetasksd quit unexpectedly” notifications. At first it happened occasionally, but it has now become extremely frequent. After dismissing one crash notification, another system service often crashes shortly afterward. I’ve also seen services related to Intelligence / intents crashing. The notifications keep appearing one after another to the point where I’m barely able to use the Mac normally — including difficulty typing and interacting with applications. The issue is not limited to Xcode. It appears to affect macOS system services themselves. System information Mac: Mac15,2 (Apple silicon) macOS: macOS 27.0 beta, build 26A5388g Xcode: Xcode 27 beta Issue started: After running the macOS beta for some time; it has progressively become more frequent Main process initially crashing: intelligencetasksd Path shown in crash report: IntelligenceTasksEngine.framework/Support/intelligencetasksd Exception: EXC_BREAKPOINT (SIGTRAP) I have attached a screenshot of the crash report showing the intelligencetasksd crash. Has anyone else experienced this on macOS 27 beta? Is there a known issue with the new Intelligence/Intents services, or is there a recommended way to reset/rebuild the relevant system components? At this point the repeated crashes are making the Mac extremely difficult to use, so I’d really appreciate any troubleshooting steps or information about whether this is a known beta issue. Thanks!

I tried to upload my build into testflight with XCode -> Product -> Archive -> Distribute App but this error keeps showing up: "No Team Found in Archive, Use the Signing & Capabilities editor to assign a team to the targets and build a new archive." However, my Apple ID IS connected and the bundle ID is the same as in my App Store Connect. What can I do? I tried deleting all archives, restarting Xcode & my Mac, still nothing happend. I can't get it to upload...

Hello! I'm new to xcode and am developing an iOS app. I hit the following error when build my app: MY_SHA no identity found Command CodeSign failed with a nonzero exit code I have generated my certificate through xcode. I can see the Certificate and the private key in Keychain -> login. But it's not that private key is under the Certificate. They are listed in parallel. The certificate appears in Certificate tab but not in My Certificate Tab. Would that matter? security find-certificate -a -Z | grep -A1 "Apple Development" Gives me the certificate. But security find-identity -v -p codesigning give 0 valid identity found. Could you help me figure out what could be the reason for this? I've been stuck for several days now. Thank you so much!

I can't find the "Show live issues" that was under "General > Issues > Show live issues [toggle]" It is present in Xcode 26.6 but not in Xcode 27 beta 5

I have an app with a Widget Extension. Both the main app and the widget extension link against the same Swift Package, which contains a localization bundle (String Catalog) used by SwiftUI views inside the package. To make the package's views follow the app's configured language (rather than the system language), I set CFBundleAllowMixedLocalizations to NO in the Info.plist of each target (main app and widget extension). Behavior in the main app: This works as expected. If the app only supports Korean, the package's views display Korean text even when the system language is set to English. Behavior in the widget: The same views (from the same package) display English instead of Korean, even though the widget extension has the identical CFBundleAllowMixedLocalizations = NO setting and the widget's view code lives entirely in the package — not in the widget extension target itself. Question: As far as I understand, widgets are supposed to follow the host app's language setting. Given that both targets have the same Info.plist configuration, why would the widget extension resolve localized strings differently from the main app for code in the same package? Is this expected behavior for widget extensions specifically, or a bug? Is there a recommended workaround to force a widget extension (and by extension, the Swift Package code it runs) to use the app's language instead of the system language?

I've been trying for months to get Gemini 3.5 Flash to work with Xcode 27 Beta (1-3) agentic coding but have failed. Xcode currently uses Gemini CLI v0.42.0 from last year, so it can't call Gemini 3.5 Flash even though all that needs to change is a few characters in the API call. Gemini users are currently forced to choose between 3.1 Pro and 3.1 Flash Preview--both weren't the best choices two months ago, but with the release of 3.6 Flash which is better at coding that 3.1 Pro and miles cheaper, these choices are now unsuitable for any serious workload. I live in Hong Kong, where OpenAI and Anthropic services aren't offered, so Google is the only (native) AI provider for Xcode agentic coding. The cost issue from funneling all the work into 3.1 Pro is terrible especially with some agent bugs that have yet to be ironed out. Given Apple's close partnership with Google on AI, I'm genuinely surprised that after 4 Betas we're still using a Gemini CLI from 2025 that forces users to choose between two very unappealing models. Xcode is basically forcing Google users to switch to OpenAI/Anthropic. Questions: I'd like to know if this will be fixed soon and whether Google users should expect slower updates (i.e. be forced to use older models). Does anyone know of any workarounds?

I am experiencing an App Store submission issue after updating my Mac development environment. A build of my iOS app can be uploaded and appears in App Store Connect/TestFlight, but when I try to use the build for App Review, it is rejected because it was built using a beta version of Xcode. I am currently using Xcode 27 beta because of the macOS environment installed on this Mac. I have been advised that I may need to return the Mac to a stable macOS/Xcode environment and rebuild the app. This is particularly concerning because the app and its development data already exist on this Mac, and reverting the development environment may require a full backup and OS reinstallation. I would like to know: What is the officially supported procedure to return to a stable macOS and Xcode environment without losing development data? Which stable Xcode version should be used to rebuild the app for App Store submission? Is there any supported way to submit the existing build, or must it be rebuilt completely with a non-beta Xcode? I would also like to know whether other developers using the current beta environment are experiencing the same App Store Connect submission restriction. I would also like clarification regarding responsibility and remediation in this situation. If a development environment provided through Apple’s software update or beta distribution results in an existing application becoming unable to be submitted to App Store Connect, what responsibility does Apple assume for the resulting disruption to developers? In particular, if resolving the issue requires backing up development data, reinstalling macOS, reinstalling Xcode, and rebuilding the application, does Apple provide an official recovery procedure or support for developers affected by this situation? I believe this is important not only for my application, but also for other developers who may encounter the same issue. I would appreciate an official clarification from Apple regarding both the technical solution and Apple’s policy for developers affected by this problem. Thank you.