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...

Hello! I've been trying to automate tests using Appium/XCUITests in a React Native APP, but I'm finding many blockers. They are related to the amount of nested elements in the "DOM" in which the XCUItest can not go deeper to get all the elements we need. snapshotMaxDepth -> The XCUITest does not support more than 60 value, otherwise it returns the following error: Got response with status 404: {"value":{"error":"stale element reference","message":"The previously found element "Application 'xyz.xxx.xxx'" is not present in the current view anymore. Make sure the application UI has the expected state. Original error: Error kAXErrorIllegalArgument getting snapshot for element <AXUIElementRef 0x600003aaf750> {pid=95967} {uid=[ID:1 hash:0x0]}","traceback":"(\n\t0 CoreFoundation 0x00007fff20405604 __exceptionPreprocess + 242\n\t1 libobjc.A.dylib 0x00007fff201a4a45 objc_exception_throw + 48\n\t2 WebDriverAgentLib 0x000000010a3caa53 -[XCUIElement(FBUtilities) fb_takeSnapshot] + 723\n\t3 WebDriverAgentLib 0x000000010a3cad07 -[XCUIElement(FBUtilities) fb_snapshotWithAttributes:maxDepth:] + 183\n\t4 WebDriverAgentLib 0x000000010a37baea +[FBXPath writeXmlWithRootElement:indexPath:elementStore:includedAttributes:writer:] + 778\n\t5 WebDriverAgentLib 0x000000010a37b12c +[FBXPath xmlRep... But if I inform less than 60, the XCUITest is not able to get all the elements we need to automate: There are many threads about this, all of them the issue is in the XCUITest: https://github.com/appium/appium/issues/14825 https://discuss.appium.io/t/handling-staleelementreferenceexception/35095/11 https://github.com/appium/appium/issues/18085 https://discuss.appium.io/t/error-in-appium-desktop-refreshing-source-after-adding-snapshotmaxdepth-greater-than-62/34058 https://stackoverflow.com/questions/74235441/appium-cant-reach-elements-in-ios-source-tree-they-are-too-deep-works-fine-in Tested all possible solutions suggested in the threads, but I will have the issue.

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

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.

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.

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

For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives "Server SSH Fingerprint Failed to Verify" as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?

I have a brand new iPhone 15 with iOS 17, paired with a watch on WatchOS10. In devices and simulators, the iPhone 15 and Watch 10 device show up as disconnected (with the globe icon I think is what it is?) and if I click on either of them, that icon changes to a spinner, and the main window says "Xcode will continue when the operation completes", but it NEVER completes. This makes the device not usable for development. In addition, I have updated my iPad to iOS17, and it doesn't even show up at all in the devices and simulator list, even though it is enabled for developer mode. I have toggled developer mode off and on (thus rebooting). I have quit and restarted Xcode. I have even rebooted the Mac. Nothing helps. This is incredibly frustrating.

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

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 ?

I switch between Project / Tests / Breakpoints using top left pane 100s times a day. I also switch to search using CMD-Shift-F. In Xcode 26.4 I have to tap the <> to open menu. Is there a way to bring back the old behavior. Does any of the UX guys who worked on that feature use Xcode on daily basis? This is so bad :(

I am using objective-c to develop a custom keyboard on iPhone X to run in landscape orientation. I want my to make use of the full iPhone X screen and have my custom keyboard layout extending from left edge to right edge of the screen in landscape orientation.No matter what I try, my custom keyboard layout stays confined in the safe area.What do you recommend?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?

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.

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

Xcore 26.2 run on newly installed macOS 15.7.3 (24G419) crashes when attempting to build assets backtrace

There are multiple iOS simulator runtimes located at /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime which I don't need. I tried the following approaches to delete them but not working. Xcode > Settings > Components > Delete (It can delete some but not all of them) xcrun simctl runtime list (It doesn't show the old runtimes) sudo rm (Operation not permitted) sudo rm -rf cc1f035290d244fca4f74d9d243fcd02d2876c27.asset Password: rm: cc1f035290d244fca4f74d9d243fcd02d2876c27.asset/AssetData/096-69246-684.dmg: Operation not permitted rm: cc1f035290d244fca4f74d9d243fcd02d2876c27.asset/AssetData: Operation not permitted rm: cc1f035290d244fca4f74d9d243fcd02d2876c27.asset/Info.plist: Operation not permitted rm: cc1f035290d244fca4f74d9d243fcd02d2876c27.asset/version.plist: Operation not permitted rm: cc1f035290d244fca4f74d9d243fcd02d2876c27.asset: Operation not permitted I have two questions: Why "xcrun simctl runtime list" is unable to list some old runtimes? How to delete them?