Xcode 26.6 It's showing crashes from the App Store Analytics. But no crash logs from Xcode Organizer. I have tried to sign out and log in to Xcode again. I also changed the folder /Library/Developer/Xcode/Products and View > Reload the Organizer. Nothing helps. It's still empty for all versions.

Can iOS 26.6 + Xcode 26.6 be used for automated testing? Are there any successful case studies?

I am currently using Xcode 16 (16A242d) and testing on an iPhone 7 running iOS 12.1.3. However, when I try to launch the app on the device, it crashes immediately. Below are the crash logs from the iPhone 7: 错误 11:54:55.731858+0800 kernel Sandbox: assertiond(62) System Policy: deny(1) file-read-metadata /private/var/mobile/Library/DuetExpertCenter/caches/ATXCacheFile-_ATXAppPredictor-TotalScore 错误 11:54:55.731897+0800 kernel Sandbox: assertiond(62) System Policy: deny(1) file-read-metadata /private/var/mobile/Library/DuetExpertCenter/caches 错误 11:54:55.754498+0800 kernel Sandbox: duetexpertd(132) deny(1) mach-lookup com.apple.proactive.ActionPrediction.predictions 错误 11:54:55.756102+0800 duetexpertd Unable to remove recent engagement cache file. Error: Error Domain=NSCocoaErrorDomain Code=4 UserInfo={NSFilePath=, NSUserStringVariant=, NSUnderlyingError=0x100db60a0 {Error Domain=NSPOSIXErrorDomain Code=2}} 错误 11:54:56.571640+0800 symptomsd Attempt to add an app with insufficient id, info { BKSApplicationStateAppIsFrontmost = 1; BKSApplicationStateExtensionKey = 0; SBApplicationStateDisplayIDKey = "com.igetcool.app"; SBApplicationStateKey = 8; SBApplicationStateProcessIDKey = 696; SBApplicationStateRunningReasonsKey = ( { SBApplicationStateRunningReasonAssertionIdentifierKey = UIApplicationLaunch; SBApplicationStateRunningReasonAssertionReasonKey = 10000; } ); SBMostElevatedStateForProcessID = 8; } 错误 11:54:56.829372+0800 assertiond [IGCProject:696] SyscallError: setpriority(PRIO_DARWIN_ROLE, 696, 3): No such process 错误 11:54:56.944833+0800 dasd Activity not tracked as being started, ignoring it 错误 11:55:06.153790+0800 symptomsd Attempt to add an app with insufficient id, info { BKSApplicationStateAppIsFrontmost = 1; BKSApplicationStateExtensionKey = 0; SBApplicationStateDisplayIDKey = "com.igetcool.app"; SBApplicationStateKey = 8; SBApplicationStateProcessIDKey = 697; SBMostElevatedStateForProcessID = 8; } 错误 11:55:06.430433+0800 assertiond [IGCProject:697] SyscallError: setpriority(PRIO_DARWIN_ROLE, 697, 3): No such process 错误 11:55:13.158889+0800 symptomsd Attempt to add an app with insufficient id, info { BKSApplicationStateAppIsFrontmost = 1; BKSApplicationStateExtensionKey = 0; SBApplicationStateDisplayIDKey = "com.igetcool.app"; SBApplicationStateKey = 8; SBApplicationStateProcessIDKey = 699; SBMostElevatedStateForProcessID = 8; } 错误 11:55:13.416290+0800 assertiond [IGCProject:699] SyscallError: setpriority(PRIO_DARWIN_ROLE, 699, 3): No such process I am trying to understand what is causing this issue. Even after archiving and installing the app, it still crashes. According to the official documentation, Xcode 16 is supposed to support iOS 12, but this issue persists. I would like to know the possible reasons for this behavior.

Hi everyone, I'm trying to run a Mac app UI tests on our CI servers (Mac minis). The servers are logged in, but the lock screen is active (aka, the active process is the com.apple.loginwindow). UI tests end up failing with: Failed to activate application (current state: Running Background) Is there any way to run Mac UI tests on a server like this without having to disable the lock screen? Our admins will likely not accept that solution, and I agree with them. Aside from running a full VM just for the UI tests, I can't find any solution. Thank you, Miguel Arroz

Sometime recently our XCUITests started to hang after awhile and so I had filed this Feedback ticket. With the release of Xcode 15.3 I re-ran the test in the project I had attached to that Feedback ticket (which taps a "Go!" button which pushes a new view controller and then verifies the value of a UILabel) and the tests are running crazy slow on a device now running iOS 17.4. It has been half an hour and only 14 of 100 iterations have been run. Anyone else experience severe performance degradation in their XCUITests with Xcode 15.3?

Filed FB24179855 for this. Posting here so others hitting similar limitations can track and/or reference it (Apple's triage reportedly weighs duplicate count). Issue <stdbit.h>, the C23 standard header for bit-manipulation utilities (stdc_leading_zeros, stdc_count_ones, stdc_bit_width, etc.) from C23 §7.18, is not present in the macOS SDK libSystem. Worth noting this is a libc/SDK gap, not a compiler gap. Apple Clang accepts -std=c23 fine, and <stdckdint.h> (also C23, also library-level, e.g. ckd_add) is already present and working correctly. So C23 library headers are clearly being landed in libSystem incrementally. stdbit.h just hasn't made it in yet. If anyone's found a workaround (other than falling back to __builtin_clz/__builtin_popcount etc.) or has visibility into whether this is scheduled, would be good to hear. Repro #include <stdbit.h> int main(void) { return stdc_leading_zeros((unsigned)0); } $ /usr/bin/cc -std=c23 repro.c repro.c:1:10: fatal error: 'stdbit.h' file not found 1 | #include <stdbit.h> | ^~~~~~~~~~ 1 error generated. Environment Apple clang version 21.0.0 (clang-2100.1.1.101) Target: arm64-apple-darwin25.6.0

Background: The app embeds an in-app game feature ("Game Hub" / Fallinmoji) that is written in Java against libGDX and cross-compiled to native code for iOS using RoboVM (via ./gradlew :ios:robovmInstall). The build produces BWIOSGdx.xcframework, which is linked and embedded into the main iOS target. What we confirmed in the framework itself: The .xcframework does contain two genuinely separate Mach-O slices — one tagged LC_BUILD_VERSION platform=IOS (device) and one tagged platform=IOS SIMULATOR (arm64 simulator), so at the packaging level Xcode sees a proper simulator slice. Despite that, the framework does not run correctly under the Simulator, so our build script deliberately skips building/linking it entirely for iphonesimulator runs ("libGDX is device-only") and the feature is device-only in practice. Root cause (working theory): RoboVM AOT-compiles JVM bytecode into native ARM64 machine code and relies on hand-written runtime scaffolding (trampolines, dynamic method dispatch, JIT-adjacent code generation) that predates Apple Silicon simulators. That scaffolding appears to assume the calling conventions/execution environment of a physical device and does not behave correctly when executed inside the Simulator's process (which runs under different memory-protection/JIT and code-signing rules than a device). The result is that even though a correctly-tagged simulator slice exists, code compiled by RoboVM's toolchain does not execute reliably there — RoboVM itself has been effectively unmaintained since ~2017 and was never updated for Apple's current arm64 Simulator runtime. Impact: We cannot build/run/debug the Game Hub feature (and by extension, sometimes the whole app when this framework is force-included) in the Simulator, which blocks fast local iteration, CI-based UI testing, and any workflow that depends on Simulator rather than a provisioned physical device. Ask for Apple: Is this a known/expected limitation of running JIT-adjacent or non-Apple-toolchain-compiled native code (e.g., from RoboVM or similar Java→native cross-compilers) inside the iOS Simulator on Apple Silicon, versus on a physical device? Is there a supported mechanism (entitlement, code-signing flag, JIT-related capability) that would let such a framework execute correctly under Simulator, or is Simulator execution of dynamically-generated/trampoline-based native code from third-party toolchains fundamentally unsupported?

My app setup is similar to https://forums.developer.apple.com/thread/133495 - I have an app target, some frameworks and local Swift packages. I added the package tests to the test plan.Now, when "gather code coverage" is just "on" in the test plan, I get code coverage from the package targets. But when I selectively add only the targets I want (including the package targets), the package targets don't show up in the code coverage results at all.Gathering code coverage for all targets isn't really what I want, because that includes a lot of third-party code that I'm not interested in.

Hello, while creating an app for backgrounds, it seems as for the lock screen live wallpaper, if I lock my screen, it plays for 1 sec then fails. Like it goes permanently black until my watchdog detects and kills wallpaperagent for it to function again. With the watchdog disabled, it’s just 1 sec after I lock my screen, it turns black, then I have to kill wallpaper agent for it to even start again. Any fixes please?

I have this local agent using Qwen 3.6 (the version that is ~17 GB). Last time I tried using this a couple months ago it worked ok. Now the agent frequently does not know how to edit a file. It takes its proposed changes and completely overwrites the entire source file with the change instead of just modifying the portion of the source code. Sometimes the agent thinks it doesn't have permission to make a change and wants me to copy and paste code. Is there an Xcode skill provided somewhere that I can use with the Agent so it knows how to work in this environment properly? Currently I have it set up via "Chat" with "Tools Enabled" and "Automatically apply changes" is on.

Setup the target as follows: Architectures = Standard Architectures (Apple Silicon, Intel) Build Active Architecture Only = No When you display $ARCHS using the Run Script added at the end of Build Phases, you will see the following differences: from GUI(Xcode.app) ARCHS=arm64 from CUI(xcodebuild) ARCHS=arm64 x86_64 Even when built from the GUI, it should be the same as when built from the CUI.

Our iOS app uploads successfully to App Store Connect and appears in TestFlight, but it crashes immediately on launch. App name: Axioma Pay Bundle ID: uk.co.axiomapay.app Distribution: TestFlight Framework: Expo / React Native Device tested: iPad via TestFlight The app installs, the icon appears, but tapping Open causes an immediate crash. One earlier build displayed this runtime message: Cannot read property 'ErrorBoundary' of undefined Crash logs show the app aborting on the React Native ExceptionsManagerQueue with SIGABRT / EXC_CRASH. We do not currently have a focused minimal Xcode sample project because this is an Expo/EAS React Native production build. We can provide .ips crash logs and App Store Connect/TestFlight build details. Can Apple help confirm whether this crash appears to be caused by: App Store/TestFlight processing, provisioning/signing/entitlements, an iOS runtime issue, or an app-side React Native JavaScript startup exception? Latest TestFlight build crashes immediately after launch.

Hi everyone, I recently updated to Xcode 26.0 and noticed that the “Extract Subview” refactoring option seems to be missing. Now, in Xcode 26, the only options I see under Editor -> Refactor -> are: Extract to Selection File Extract to Method Extract to Variable Extract All Occurrences But there’s no Extract Subview as there was before. Was Extract Subview intentionally removed in Xcode 26? Or is it hidden behind a new menu location or renamed?

Accepting a proposal in chat switches windows and no code change applied. (hoping part of issue might be chat window takes over right side rather than swapping with navigator like before in previous Xcode 26.5

It seems like Apple changed the UI for iOS TestFlight today. I uploaded a build that has completed processing, it appears in the selection list, but I am not able to select it. The radio buttons just don't react. Anyone?

Hi, We ship an iOS and iPadOS app distributed on the App Store. We understand new submissions will be required to use the Xcode 27/iOS 27 SDK starting around April 2027 (following the same pattern as the iOS 26 SDK requirement from April 2026), after which the UIDesignRequiresCompatibility flag will no longer be available. Is there an exact date this takes effect? Specifically, will submissions built with Xcode 26 still be accepted in March 2027, or is the cutoff earlier? Thank you.

Bitbucket recently moved from App Passwords to API Tokens. When I try to access my Bitbucket Cloud account from Xcode 26.6 it does not offer the option to connect using an API Token. I am therefore unable to access my packages stored on Bitbucket.

I've recently updated to Xcode 26.3 and I can't download any iOS Simulator Runtime from 26.2 to 18.0, every download gives me: Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2026-03-03 16:14:50 +0000"; } -- Download failed. Domain: DVTDownloadableErrorDomain Code: 41 -- System Information macOS Version 26.4 (Build 25E5218f) Xcode 26.3 (24587) (Build 17C529) Timestamp: 2026-03-03T17:14:50+01:00 I tried cleaning every cache, and logging in and out of my account. I saw some reddit posts where they suggested to check out VPNs, host files and other stuff but everything was okay, also I can reach apple cdns etc. I also tried using Xcode beta 26.4 and going back to 26.2 but still the same problem. Anyone has a solution?

#include <stdio.h> void test50() { unsigned int b = 0x7d40d133; unsigned int m = 0x22e5bbf; unsigned int r = 64; b += (((m) << ((int)(r))) | ((m) >> (32 - (int)(r)))); // expect b = 0x7f6f2cf2, however in opt bigger than O1, b = 0x819d88b1 printf("%#x\n", b); } int main() { test50(); return 0; } Compiling with -O0 and -O1 produces different results. There appears to be a compiler optimization bug that is triggered when r % 32 == 0，This feature works correctly in Xcode 26.0.

ご指定の挨拶や結びの言葉をすべて除外した、本文のみの英文です。 I am writing to inquire about the debugging workflow for background processing in recent versions of Xcode. In previous versions of Xcode, we were able to test the behavior of background fetches using the "Simulate Background Fetch" option under the Debug menu. However, this menu item is no longer available in the latest Xcode environment. Our application requires executing background tasks, such as automatically transferring images captured during background transition to a remote server. We are currently in the process of migrating our background structure to the latest BackgroundTasks framework (BGTaskScheduler) in accordance with the recommendations in the official documentation. Now that the GUI menu item has been removed, could you please provide the official guidelines or recommended workflow for simulating and debugging BGAppRefreshTask and BGProcessingTask on the iOS Simulator? Specifically, I would like to know if executing specific LLDB commands while the process is paused is the only supported method to simulate these events during development.