It annoys me that Xcode keeps downloading Simulators automatically, even though I haven't asked for them. Under Settings > Components > Other Installed Platforms I see iOS Simulator iOS 18.0 uptil 18.5. These are eating space in /Library/Developer/CoreSimulator/Caches/dyld/25E253. Is there a way to prevent these automatic downloads?

Codex will no longer be available in Xcode 26.3 starting on Friday, May 8th. Please upgrade to Xcode 26.4 or later to continue using Codex.

I inherit from a protocol that implements in its extension those functions, that should not be required by the adopting class and instead I get those errors. Could someone explain why those errors appear and how to fix it.

Is there any solid documentation to get the controllers to work in my experience? I am having the hardest time figuring out how to get the controllers to work properly. I get them to work in the system, but within my project, they work, but inconsistent and some buttons will not register taps, grabs, grips, etc

After enabling Enhanced Security for an existing iOS project (mixed Objective-C / Swift) I get the linker error: Library 'c++polyfills' not found This happens when compiling for a simulator as run destination. Device builds (debug) or archiving a release build works. However I need to be able to test on a simulator... Xcode version is 26.4.1, Simulator uses iOS 26.4.1

I just noticed this but am curious: Why does Xcode use list.bullet SF Symbol to toggle the "navigators" (sidebar) instead of sidebar.left? For the inspectors Xcode uses "sidebar.right" but I don't understand why the left sidebar uses a different icon from the right sidebar? Shouldn't the left sidebar icon match the right sidebar (just flipped)? Am using the wrong SF Symbol in my app to toggle the sidebar? Is the list.bullet the recommended symbol for this now? Every other app seems to use sidebar.left.

We came across reports on Medium and Apple Developer Forums suggesting that ApplicationToken and ActivityCategoryToken values issued by the FamilyControls framework are not guaranteed to be stable, that iOS may silently re-issue new tokens for the same apps after OS or app updates, making any previously stored tokens invalid. We are storing FamilyActivitySelection tokens encoded via JSONEncoder to a backend for long-term use, and relying on them inside a DeviceActivityMonitorExtension to restore and apply shields when a schedule fires. What we're trying to understand is: is this token instability still an active problem in iOS 16/17/18/26, and when a token does become invalid, does JSONDecoder actually throw a DecodingError giving us a clear signal, or does it decode successfully and ManagedSettingsStore just silently ignore the stale tokens with no error at all? On Medium, We Found That The Token Mutation Problem One of the more painful bugs in real production apps: application tokens are not guaranteed to be stable forever. iOS can silently issue new, different tokens for the same app. If your store contains the old token and the Shield delegate receives a new one, the delegate has no way to match them — it doesn’t know which store is responsible for the shield, or which blocking “profile” caused it. This has been reported by multiple developers of real Screen Time apps and confirmed across several Apple Developer Forum threads. There is no official fix yet. The workaround is defensive: when the ShieldConfigurationDataSource or ShieldActionDelegate receives a token you don't recognise, fall back to a generic shield UI rather than crashing or returning empty data. And never rely on token identity as a long-term stable key in your persistence layer — always re-derive from a fresh FamilyActivityPicker selection when the user re-activates a profile.

Hello. I don't know if this is a place to ask questions and get solutions, but I think there will be a lot of experts gathered, so I'm posting it. I'm a student who recently started learning Xcode. In the book, you can see a graph-shaped pop-up window by pressing the eye-shaped quick look button in the Xcode playground, but I can't find that button in my Xcode 26 version. Can you tell me where the button is? I'm sorry for asking such a basic question.

When signing in to GitHub.com in Xcode, it shows what scopes must be set when creating a personal access token. However, when signing into GitLab.com, it doesn't show what scopes should be selected.

Currently, when creating a new Git remote in Xcode, the visibility for the new repository is set to public by default. It would be safer if it were set to private by default. FB22673051 https://github.com/feedback-assistant/reports/issues/797

Xcode 26.4.1, iOS 26.4.2, watchOS 26.4, Apple Watch Ultra 3 not appearing as development device. Can't do any IWatch development

Hello, My request to get the family control entitlement for distribution has been approved on June 30, 2025, for my app with bundle id io.onelife.app.ios. I added a device report extension to it recently, but since then I'm not able to upload a new archive to testflight. The upload fails with error: exportArchive Provisioning profile "iOS Team Store Provisioning Profile: io.onelife.app.ios.YoholDeviceActivityReportExtension" doesn't include the com.apple.developer.family-controls entitlement. I ticked the checkbox in developer.apple.com -> identifiers -> YoholDeviceActivityReportExtension -> Capability, and it seems to have created a new request 9AHY2B7947 on April 23, 2026. Did I miss something ? Should I just wait to have it approved a second time ?

On watchOS, the Developer Mode entry under Settings -> Privacy & Security is hidden by default and only appears after Xcode has attempted to connect to the watch as a development device. In my case, once Xcode triggers that surfacing, opening Settings -> Privacy & Security on the watch prompts for a 4-digit Screen Time passcode before granting access. No Screen Time passcode I set on the paired iPhone is accepted at this prompt, which prevents me from reaching the Developer Mode toggle to enable it. The passcode prompt only appears in this specific state. With no Xcode connection attempt (and therefore no Developer Mode entry surfaced in the menu), Settings → Privacy & Security opens normally on the watch with no prompt at all. Environment macOS: Tahoe 26.4.1 (Build 25E253) Xcode: 26.4.1 (24909.0.3) (Build 17E202) iPhone: iOS 26.4.2 Apple Watch: Ultra 3 running watchOS 26.4 All devices on release software (no betas). Xcode error Developer Mode disabled Domain: com.apple.dt.deviceprep Code: -28 Recovery Suggestion: To use [Watch Name] for development, enable Developer Mode in Settings → Privacy & Security. User Info: { DVTErrorCreationDateKey = "2026-04-30 09:38:57 +0000"; "com.apple.dt.DVTCoreDevice.operationName" = checkDeveloperMode; } Reproduction Pair Apple Watch to iPhone (paired fresh, set up as new, not restored from backup). Connect iPhone to Mac running Xcode 26.4.1. Before any Xcode connection attempt, open Settings -> Privacy & Security on the watch. The menu opens normally with no passcode prompt. There is no Developer Mode entry visible. In Xcode, attempt to use the Apple Watch as a run destination. Xcode returns the -28 / Developer Mode disabled error above and instructs me to enable Developer Mode in Settings -> Privacy & Security on the watch. After this attempt, the Developer Mode entry is surfaced in Settings -> Privacy & Security on the watch. Open Settings -> Privacy & Security on the watch in this surfaced state. The menu now prompts for a 4-digit Screen Time passcode before allowing access. The passcodes I have set on the paired iPhone are rejected. The passcode prompt is therefore conditional on the Developer Mode entry having been surfaced by a recent Xcode connection attempt. In step 3 (no surfacing) the menu opens freely; in step 6 (surfacing in effect) the menu is gated. What I have already tried Confirmed Screen Time is disabled on the paired iPhone. Confirmed Share Across Devices is enabled. Confirmed Content & Privacy Restrictions is off on the iPhone. Confirmed I am an adult in my Family Sharing group (not a managed/child account). Confirmed there are no configuration profiles installed (Settings -> General -> VPN & Device Management is empty). Set a fresh Screen Time passcode on the iPhone. Not accepted by the watch prompt. Used Forgot Passcode? → Apple ID authentication to reset the Screen Time passcode and set a new one. Not accepted by the watch prompt. Turned the Screen Time passcode off entirely on the iPhone. The watch still prompts for one when Xcode is connecting. Unpaired the Apple Watch and re-paired as new (not restored from backup). Issue persists. Tried entering the watch's own device passcode at the prompt. Not accepted. Question What credential is the watch's Privacy & Security menu actually checking against once the Developer Mode entry has been surfaced, and how can it be reset or cleared from a paired iPhone? Is anyone else seeing this conditional gating where the menu is only locked in the post-surfacing state? Any pointers from the Xcode / watchOS tools team would be appreciated. Happy to provide sysdiagnose or further details on request.

I am developing an iOS app using Capacitor and Xcode. The app installs on my device but fails to launch with the error: “Quarantined due to high logging volume.” I have already: Configured signing correctly Enabled Developer Mode Disabled excessive logging in the app code Cleaned build and re-synced Capacitor The app still fails to run on a physical device (My iPhone 17Pro Max). Please advise on how to resolve this issue or whether this is related to a system-level logging limit or WebView restriction. Please suggest a reliable solution to the issue.

Any idea why this might happen and how to stop it? I try to run a simple iOS app from Xcode, in the iOS Simulator, and it takes a very long time to start. I see "mediaanalysisd" in the Activity Monitor, taking a lot of CPU, fans are blowing. When I quit the simulator, the mediaanalysisd process goes away and the fans stop. Maybe related: I have a 2020 MacBook Pro with Intel chips, and general it's been having more bogged down performance and fans blowing that in years past. My suspicion is the latest macOS updates are not caring much about Intel CPUs...

I cannot distribute an app on xcode becouse he cannot find a certificate valid for my personal or business team. Need to address XCODE to access to my business account and not personal

Hi everyone, I'm unable to use the po or v commands in the LLDB debugger in a fresh new iOS project (but works in my existing projects). I'm using Xcode 26.2 (17C52). I tried solving the issue with various AI tools for hours but had no success. The community is truly irreplaceable.

It would be helpful if the required token scopes were pre-filled in the URL when clicking the "Create a Token on GitHub" button when signing into a GitHub account in Xcode. FB22632532 https://github.com/feedback-assistant/reports/issues/796

Description Xcode 26.4.1 crashes immediately on launch with a code signature error. The issue exists on macOS 26.4.1 and persists after upgrading to macOS 26.5 (25F5058e) and attempting 26.6 beta. Crash Details: Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page Key symbols: dyld3::MachOFile::trieWalk, dyld4::JustInTimeLoader::applyFixups, dyld4::Loader::forEachBindTarget All Steps Tried (All Failed): Fresh reinstall from Mac App Store and .xip from Developer website Multiple sudo xattr -cr + sudo codesign --force --deep --strict --options=runtime --sign - Deleted all Xcode caches, DerivedData, and preferences Tested in a brand new user account (same crash) Downgraded Xcode to older versions macOS remains on 26.4.1 (issue existed here) and upgraded to 26.5 / attempted 26.6 beta — still same crash Refreshed Apple Worldwide Developer Relations certificates Multiple restarts The crash report is identical every time. System Information Model: MacBook Pro (M1 Pro, MacBookPro18,1) macOS: 26.5 (25F5058e) — issue started after upgrade from 26.4.1 Xcode: 26.4.1 (24909.0.3) SIP: Enabled Developer Mode: Enabled Additional Notes Other applications launch normally. This appears to be a system-level compatibility issue introduced in macOS 26.5's stricter code signing validation on mapped files / chained fixups. Request Is there a known workaround? Is Apple preparing a fix in a future macOS 26.5 patch or Xcode update? What additional information would help? Thank you!

Xcode 26.3 MCP xcode-tools: RunSomeTests / RunAllTests response violates tool output schema (missing required errors per test) I’m using the MCP server “xcode-tools” shipped with Xcode 26.3 to run tests. Two tools fail consistently due to a schema mismatch: RunSomeTests RunAllTests Steps Call XcodeListWindows and get a valid tabIdentifier for my workspace. Call GetTestList with that tabIdentifier. This works and returns test identifiers like: ChatKitManagerCreationTests/testInitializesWithDependencies() Call RunSomeTests with tests = [{ targetName, testIdentifier }, …] (or call RunAllTests). Actual result The tool call fails with an MCP schema validation error like: Structured content does not match the tool's output schema: data/results/0 must have required property 'errors', data/results/1 must have required property 'errors', ... Why this looks like an xcode-tools bug According to the tool descriptor JSON for RunSomeTests / RunAllTests, each element of results[] is required to contain: targetName identifier displayName state errors (required, array of strings) But the actual response returned by RunSomeTests / RunAllTests appears to omit the errors field for one or more results (for passed tests it should still be present as an empty array []). Expected result RunSomeTests / RunAllTests always return structured content matching their declared output schema. In particular, every results[i] should include errors: [] when there are no errors. Environment Xcode: 26.3 macOS: Darwin 25.4.0 Workspace: Grocery.xcworkspace Scheme: GroceryCoreTests Active test plan: GroceryCoreTests Question Is this a known issue in Xcode 26.3’s MCP xcode-tools? Is there a workaround (e.g. alternative output mode, or reading a full summary file) until the schema/response is fixed?