build disappears

We would like to request an enhancement to Xcode Cloud workflows to support skipping builds when a GitHub Pull Request is in Draft state. Our team frequently collaborates on pull requests that go through multiple iterations during the code review cycle. Each small commit or push triggers an Xcode Cloud workflow run, even if the PR is still in draft and not ready for final review or CI validation. This leads to: Wasted compute resources and time on draft work that is not yet intended for integration. Increased noise in Xcode Cloud logs and dashboards. Longer feedback cycles for meaningful PRs, since draft workflows compete for available concurrency. A simple option in the workflow configuration (e.g., “Skip runs for draft pull requests”) would address this problem by: Reducing unnecessary workflow executions. Freeing up capacity for production-ready and review-ready builds. Improving overall developer productivity by aligning CI runs with the actual readiness of a PR. This feature would be es

Hello, I am looking to develop a relationship with a developer that has experience running through the IOS build approval process. To elaborate, my team and I have designed and built a software application which is working through the Apple Developer review process to have the app approved and released to the App Store. Unfortunately, there has been some challenges, simple challenges in my eyes with our interface preventing Apple from approving our application. Happy to elaborate further. A primary problem and solution I have seen is the software build was testing solely on the iPhone but as recently directed it seem the application must be accessible on iPad as well. With this the case, I have experience some software platforms where on the ipad the interface is not displayed on the whole screen. I am looking for direction on how to implement this setup for the 1st IOS build. Another concern from Apples Developer Review team is the App Tracking Transparency kit may need to be imple

Steps to Reproduce: Connect a MacBook Pro (lid closed) to a large external monitor. Run the SDL3 testwm test application. git clone https://github.com/libsdl-org/SDL.git cmake -S . -B build -DBUILD_SHARED_LIBS=OFF -DSDL_TESTS=ON cmake --build build The testwm binary will be located in the build/test directory. Move the application window around the left edge of the external display. Observed Result: WindowServer crashes. System Configuration: MacBook Pro M3 Max, macOS Sequoia 15.6.1 LG GX9, 5120x2160 resolution, running at 165 Hz refresh rate Lid closed, single external display Panic Log: panic(cpu 7 caller 0xfffffe0027f61d5c): mismatched swapID's 6386399 vs 6386400n @UnifiedPipeline.cpp:14570 Debugger message: panic Memory ID: 0xff OS release type: User OS version: 24G90 Kernel version: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:55 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6031 Fileset Kernelcache UUID: 8AA69CD2038CD2BAE2ED364428F4DBEA Kernel UUID: 75A21406-D046

We have had 2 Builds so far stuck archiving. Both indicate in their logs that Build Archive took a normal amount of time (9m and 19m) but the step Archive - iOS never finished. One of them ran for more than 6 days until we noticed and canceled it. The other one ran for 18 hours, and also had to be canceled manually. They were in two different projects, with no significant changes. The first build ran on Xcode 16.4 (16F6) and macOS Sequoia 15.6 (24G84), which we had had no issues like this with until just now, and the second ran on Xcode 26 (17A324) and macOS Tahoe 26 (25A354). We tested our app on the newest Xcode version and had no issues. Submitted report using feedback assistant: FB20279737.

In a new document-based macOS app project created in Xcode, some of the default system-provided menu commands appear without their standard icons in the menu bar. Steps to Reproduce: 1. In Xcode, create a new macOS “Document App” project (using Swift/SwiftUI or AppKit template). 2. Build and run the project. 3. Open the app’s main menu bar and examine the default items such as New Document, Open…, Save, Duplicate, etc. Expected Results: System-provided menu items (e.g. Open…, Save, Duplicate) should display their standard SF Symbol–based icons automatically, as they do in TextEdit and other system apps. Actual Results: Some of these menu items display only text, with no icon namely: Services Open Recent Revert To Share This happens even though the items are the system-managed defaults generated by the document-based app template. Notes: • No code modifications were made — this occurs in a fresh, unedited template project. • Behavior seen on macOS 26.0 (25A354). • Xcode Version 26.0 (17A324) used.

The app “Wi-Fi Aware Sample” on Bojie的iPhone quit unexpectedly. Domain: IDEDebugSessionErrorDomain Code: 20 Failure Reason: Message from debugger: The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log. User Info: { DVTErrorCreationDateKey = 2025-09-17 10:26:56 +0000; IDEDebugSessionErrorUserInfoUnavailabilityError = Error Domain=com.apple.dt.deviceprep Code=-10 Fetching debug symbols for BojieU7684iPhone UserInfo={NSLocalizedRecoverySuggestion=Xcode will continue when the operation completes., NSLocalizedDescription=Fetching debug symbols for BojieU7684iPhone}; IDERunOperationFailingWorker = DBGLLDBLauncher; } Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { device_identifier = 00008101-001E29E01E63003A; device_isCoreDevice = 1; device_model = iPhone13,3; device_osBuild = 26.0 (23A341); device_osBuild_monotonic = 23000

Hi there, My app update submission was stuck in Waiting for Review state for over 80 hours. Yesterday I canceled and resubmitted it again after 3.5 days of inactivity, but this time it still hasn’t moved forward. I'd like to be sure that there is no issues on my side during sending build to review, cuz I noticed that submit app flow was slightly changed a week ago. Usually app update was verified in 10-20 hours, but now it's stuck. Thank you in advance.