xcode github

This is happening to me on a fresh install of Xcode 26.2 > 13 mini (iOS 26.2). No betas here, all shipping versions.

Just checked new Xcode 26.2 with iOS 26.2 and the debug builds startup time indeed improved significantly. We still have ~7 seconds of initial sluggishness (difference between debug executable on/off), but it's way better than it was before! 👍

I investigated this further and confirmed the issue is due to a toolchain mismatch inside Xcode 26.1. Although test execution successfully generates multiple .profraw files, the coverage merge step fails. Running the merge manually using the Xcode-bundled tool results in the following error: raw profile version mismatch: Profile uses raw profile format version = 8 expected version = 10 error: no profile can be merged. The same project and test configuration generates coverage correctly on earlier Xcode versions, which strongly suggests a issue in Xcode 26.1’s coverage toolchain.

Thanks. Couldn't succeed after many tries of downloading and install (errors about permissions to read or execute...). I succeeded following the protocol described here: https://medium.com/@sergey-pekar/how-to-fix-annoying-xcode-26-not-building-swiftui-previews-error-cannot-execute-tool-metal-due-49564e20357c What I dont understand is that on my M1Max MBP, Metal was already OK without any setting, and I could compile my project once XCode 26 was downloaded and installed

The link that Albert posted has updated to include this latest entry: December 12, 2025 App Store Connect update You can now upload apps built with Xcode 26.2 using the SDK for iOS 26.2, iPadOS 26.2, macOS 26.2, tvOS 26.2, visionOS 26. 2, and watchOS 26.2 for the App Store, and for internal and external testing through TestFlight. We were able to upload and submit our app. Conclusions: This is probably a rare situation. However, it demonstrates that Xcode RC builds might not reach the point of having their archived app builds accepted for App Store submissions. If anyone from Apple is reading this, our feedback: We respect your processes and accept that it is often in Apple's and the developers' interests to not convey information that is subject to change. That said, when a pattern is established like almost always accepting Xcode RC built submissions, then expectations will become established amongst the developers. If you multiply the time spent and frustration caused across all

The tooling for Metal became an optional download with Xcode 26, as only some developers need those capabilities. If you look to Xcode > Settings > Components, and try to download and install it, what happens? The text of the error you shared there is also a command you can run in Terminal to do the same thing. If there are error messages when installing the toolchain from Xcode settings or in Terminal, please include a screenshot or the full error message text. — Ed Ford,  DTS Engineer

Thanks for the post. Upon uploading your app to TestFlight and installing it from there, all audio on your app appears to be disabled? Are you utilizing Flutter? Have you reached out to the support channel for Flutter, the third-party resource you are using? I do not believe this issue is related to TestFlight, as other apps have audio. However, if you can reproduce the issue using Xcode by creating a focused sample and uploading it to TestFlight to verify the presence of audio, that would be helpful. A focused Xcode project that builds and demonstrates the issue. Ideally this will be a new Xcode project created specifically to demonstrate this issue, and which includes only the minimal code and API necessary to reproduce the issue. This focuses on the important code paths and may require you to perform additional debugging to extract the relevant code. Please do not include any 3rd-party code or frameworks unless they are absolutely required for this targeted sample project to run.

Uploads to App Store from Xcode 26.2 build 17C52 are working now! I was also seeing the same error 2 hours ago.

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

I am tracking some other issues related to localStorage. Please consider filing a bug report. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

1 - We implemented the code to upload still images. We would like to do the same for Live Photos, but we are not sure how to proceed since a Live Photo is composed of 2 resources that we would like to upload in the same job so that we keep the association between the 2 resources. I think your only option here is to process the assets as separate jobs and use the URL request to preserve the conceptual link between the assets— for example, embedding that information in the upload URL or in the URL metadata. 2 - Is there a way to synchronise the application and the extension so that the application would not process the same data or execute the same requests as the extension? For example: our application is working with tokens, and we would like to prevent those tokens from being consumed by the application and the extension at the same time. These issues are alluded to at the end of this section where it says: Important: Your extension needs a mechanism to track which assets you’ve already processed and detect