When i am trying to archive a framework for ML, using below command: xcodebuild -workspace "./src/MLProject.xcworkspace" -configuration "Release" -sdk "iphoneos" -archivePath "./gen/out/Archives/Release-iphoneos/MLProject" -scheme "MLProject" -derivedDataPath "./gen/out/" archive BUILD_LIBRARY_FOR_DISTRIBUTION=YES SKIP_INSTALL=NO The same command used to work fine on Xcode 16.4. Attached is the detailed error MLProject_Archive_failure.txt

Hello I have a problem with provisionprofile file. I have created Identifier with Sign in with Apple capability turned on, created Profile with Developer ID selected and now I try to export archive with generated Developer ID provision file but it says "Profile doesn't support Sign in with Apple" Also interesting thing that default provisions like macOS App Development Mac App Store Connect don't show such error when I try to export archive Maybe this problem is only related to Developer ID provision and Direct Distribution doesn't support Sign in with Apple, but I havent found proves about this idea

I have an iOS app with a QuickLook extension. I also added Apple Vision Pro in the target's General > Supported Destinations section. About one year ago, I was able to run the app on iPhone, iPad and Apple Vision Pro Simulators. Today I tried running it again on Apple Vision Pro with Xcode 26.0.1, but Xcode shows this error: Try again later. Appex bundle at ~/Library/Developer/CoreSimulator/Devices/F6B3CCA8-82FA-485F-A306-CF85FF589096/data/Library/Caches/com.apple.mobile.installd.staging/temp.PWLT59/extracted/problem.app/PlugIns/problemQuickLook.appex with id org.example.problem.problemQuickLook specifies a value (com.apple.quicklook.preview) for the NSExtensionPointIdentifier key in the NSExtension dictionary in its Info.plist that does not correspond to a known extension point. I tried again later a couple times, even after running Clean Build Folder Immediately, without any change. I can reproduce this with a fresh Xcode project to which I add a Quick Look Preview Extension and Apple Vision Pro as a supported destination. The error doesn't happen when running on Apple Vision Pro (Designed for iPad) or iPad Pro 13-inch (M4) destinations. What is the problem? I created FB20448815.

Hello, I appreciate the enhanced productivity brought by ChatGPT and Claude AI integration in Xcode 26, which assists with code completion, refactoring, and documentation directly within the IDE. However, in real-world development environments, teams use a variety of MCP (Model Context Protocol) collaboration tools such as Jira, GitHub, Notion, and Confluence. Currently, there is no official, seamless integration of multiple MCP services with the AI features inside Xcode. For example, it would be extremely beneficial if: AI could automatically fetch and understand issues, tickets, documents, and code context from multiple MCP services, Perform related code modifications, pull request creation, and documentation updates All done intuitively and with minimal steps directly from Xcode. I kindly request that future Xcode releases provide official support for connecting to various MCP APIs, enabling smoother collaboration between AI and multiple team productivity tools all within the IDE environment. Thank you for considering this enhancement.

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?

I have 2 app store connect apps: "" ".beta" This is necessary for our usecase as we are building an iOS blockchain wallet, for a chain that updates itself every ~3 months adding new features/changing. We need the communities input, and can't have them uninstalling/re-installing the production app constantly, having to re-import private keys, etc. So we use 1 app store connect app for production releases, and another for public facing long running beta, where we experiment with new features before pulling them into production. Allowing users to have both installed at the same time Last week my CI (without any changes to scripts, project, profiles, etc), started failing for the production build with the error: [altool.105176BE0] Validation failed (409) This bundle is invalid. The bundle identifier cannot be changed from the current value, '<bundle-id>.beta'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect. (ID: ae60bab4-0c01-4b2e-9ea9-91a73adccc14) Nowhere in any of the .app, .ipa, info.plist, provisioning profiles, etc, is it referencing ".beta", everything is referencing "" I tried building it manually locally, same error. I took the local output that failed with xcrun altool, and instead dropped it into Transporter, and it uploaded successfully to the production app Is it possible that xcrun altool is using an app store connect API that changed sometime in the last few weeks? Maybe the search/sort ordering logic has changed?

After switching from Xcode 16 to Xcode 26, the app crashes. It runs normally in Xcode 16 but crashes in Xcode 26. The stack trace is below. dyld[29371]: Library not loaded: /usr/lib/swift/libLiveExecutionResultsLogger.dylib Referenced from: /private/var/containers/Bundle/Application/306FCC79-E84A-4C54-ACBE-D1EC6A469560/BoxPlayer.app/BoxPlayer.debug.dylib Reason: tried: '/usr/lib/system/introspection/libLiveExecutionResultsLogger.dylib' (no such file, not in dyld cache), '/usr/lib/swift/libLiveExecutionResultsLogger.dylib' (no such file), '/private/preboot/Cryptexes/OS/usr/lib/swift/libLiveExecutionResultsLogger.dylib' (no such file), '/usr/lib/swift/libLiveExecutionResultsLogger.dylib' (no such file, not in dyld cache)

Hello! Ive been working on a package tracking app for iOS and was looking forward to pushing it to TestFlight for some testers to use. When I go to archive the package, I get a warning about the "...TrackerIntents.appex is an ExtensionKit extension and must be embedded in the parent app bundle's Extensions directory, but is embedded in the parent app bundle's Tracker.app/Extensions directory". The extension is for siri integration with shortcuts. I have done quite a lot of things to try and diagnose this but cant seem to get passed this warning. I know it's a warning but would rather it not exist. Ideally I would think its a matter of "moving" the items but in the navigation area, I dont see an extensions area. The main app target has it in the dependencies along with the EmbedExtensionKit Extensions in the Build Phases. Any ideas or configs I can try? I can provide more information if needed. This is on the latest Xcode version 26.0.1 for iOS 26. Thank you.

I have an AppleTV app which I released in 2016. I've updated it and released a new version every year without much hassle. This year, with tvOS 17.2, the layered app icon isn't working right. This is a two-layer image made with PNGs. When it's selected, it looks right and the layers move correctly: But when it's not selected, the background layer disappears: Screenshots are from the simulator but it also happens on the device. It's inconsistent; sometimes it's the front layer that disappears. Occasionally both layers work, but I can't tell why. I've spent a day trying everything. Very frustrated. The icon previews correctly in Xcode and in Parallax Viewer. The image sizes are correct: 400 x 240 for Small, 800 x 480 for Small@2x, 1280 x 768 for Large. The back layer is a non-transparent PNG. I tried adding a Large@2x set. Didn't help. Originally I had a three-layer image with no middle layer PNG. I deleted the empty middle layer, but that didn't help. All the PNG files are from GnuIMP. Same color space, even. I was using the filenames tvicon-back-s.png and tvicon-back-s@2x.png. I tried taking out the @ sign in case that was confusing Xcode. (It never has before, but I am flailing here.) Anybody have any clues? If it's an Apple bug and there's nothing I can do, I'm going to just push the release button and hope it fixes itself someday.

When running unit tests or UI tests that cause a crash (even intentionally), the simulator itself crashes and can't be booted again in subsequent runs. This started happening from Xcode 26, our project never had this issue before (we had crashes before as well). Steps to Reproduce: Run the unit test with fatalError(). Observe the simulator crashes. On the next test run, the simulator fails to boot, remaining in a crashed or stuck state. Example error: error = Error Domain=FBSOpenApplicationServiceErrorDomain Code=1 "Simulator device failed to launch com.xxx.xctrunner." UserInfo={NSLocalizedDescription=Simulator device failed to launch com.xxx.xctrunner., NSUnderlyingError=0x600009895830 {Error Domain=FBSOpenApplicationServiceErrorDomain Code=1 "The request to open "com.xxx.xctrunner" failed." UserInfo={BSErrorCodeDescription=RequestDenied, NSLocalizedDescription=The request to open "com.xxx.xctrunner" failed., NSUnderlyingError=0x6000085d9500 {Error Domain=FBProcessExit Code=64 "The process failed to launch." UserInfo={NSUnderlyingError=0x60000850b360 {Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo=0x600008999340 (not displayed)}, BSErrorCodeDescription=launch-failed, NSLocalizedFailureReason=The process failed to launch.}}, FBSOpenApplicationRequestID=0xbe36, NSLocalizedFailureReason=The request was denied by service delegate (SBMainWorkspace).}}, NSLocalizedFailureReason=The request was denied by service delegate (SBMainWorkspace)., FBSOpenApplicationRequestID=0xbe36, SimCallingSelector=launchApplicationWithID:options:pid:error:, BSErrorCodeDescription=RequestDenied})

I am trying to run the simple demo app from xcode on my Apple Watch SE 1st gen, which has WatchOS 10.6 This turned out to be an impossible mission. I have xcode 16.1 installed, can't downgrade to 15.4 (which is the latest that supports this os) since it won't run on my OS (Sequoia), using parallels I installed Sonoma and xcode 15.4 but it won't recognize my iphone or my watch. Asking ChatGPT it seems that it is possible to use the DeviceSupport watchOS 10.6 image if I get it from someone, but loading it up "the right way" on my machine turned out to be impossible. Any recommendations / help / link to this file where I can download it?

Hi, is there a compiled version of MailCore.swift? I want to build an easy-to-use mail app for my mother, who is 97, has a MacBook Air, but Apple Mail is too complicated for her. chatGPT said I am too stupid to compile it by myself. Regards Stephan

Hi everyone, I created my app icon using Apple’s Icon Composer tool, a single AppIcon.icon file, set the iOS and Mac Catalyst using shared mode. There’s no AppIcon imageSet in Assets.xcassets. The app displays the icon correctly at runtime — both on iOS devices and on macOS (Catalyst build). On macOS versions prior to 26, the App Store icon looked completely normal. However, in App Store Connect and in the Mac App Store on macOS 26, the icon appears with a gray border. Thanks in advance for any insights or suggestions!

Hi everyone, My app notarization has been stuck in the “In Progress” state for the past 4 days. Here are the details: createdDate: 2025-10-12T07:56:46.228Z id: 8f8c9a33-1c72-489e-a189-74c797a12fbc name: DevScribe.zip status: In Progress I checked the Apple System Status page and noticed that the Developer Notarization service has been showing an outage since October 8th. Could this ongoing outage be the reason my notarization is stuck? Is anyone else experiencing the same issue? Any guidance or workaround would be greatly appreciated.

Hi, I built my app using vs code, how can I open/import to Xcode? The app is a simple game app.

When I start a Simulator (iPhone 13 mini) with iOS 26 and activate "Use the Same Keyboard Language as macOS", it still sets the keyboard to US (my Mac keyboard is in German). This makes the Mac keyboard unusable. It looks like a bug, because it clearly ignores the settings. When I type “@”, I get “¬”. Restarting the simulator did nothing, changing the settings back and forth also. BTW: Why does every single update of XCode come with a bug nowadays? I always have to spend half a day after an update to fix a problem I didn't have before. Highly frustrating.

I have an environment variable set in an xctestplan for a set of unit tests that I access like so: let testType = ProcessInfo.processInfo.environment[TARGET_TEST_TYPE_KEY] This is always is always returning nil when I run my unit tests in Xcode 26, but seems to work as expected in Xcode 16.4. Were there any changes in Xcode 26 that changes how this works? Thanks in advance.

My app start up has became horrid. It takes 1 minute to open SQLlite database for my rust core. Impossible to work... I have Address Sanitizer, Thread Perf Checker and Thread Sanitizer disabled...

For the last week, every Update to Latest Package Version ends with the error fatal: unable to access 'https://github.com/firebase/firebase-ios-sdk/': Failed to connect to github.com port 443 after 31891 ms: Couldn't connect to server. This could be firebase-ios-sdk or another package. The timeout in the example given is 31,891 ms, but it could be more than 75,000 ms. However, other packages from GitHub are updated without errors. The next attempt may return the same error with the same repository, or with a different one, while the repository from the previous attempt is updated normally. This only happens in Xcode; pure Git performs clones (with and without mirrors), fetching, pulling, and any other actions permitted without any error. What happened, and how can I restore normal package management? MacOS 26.0.1 xcode 26.0.1

The following C code shows different results when build in debug or release mode with Xcode 26.0.1. #include <stdio.h> static void print_fval(int16_t *src) { float fval = (float)((((int32_t)*src) << 16) - (1 << 31)); printf("fval: %f\n", fval); } int main(int argc, const char * argv[]) { int16_t i16[1] = { 0 }; print_fval(i16); return EXIT_SUCCESS; } In debug mode the output is: fval: -2147483648.000000. In release mode the output is: fval: 2147483648.00000. The 1 << 31 might be questionable but I would expect the same outcome in debug or release mode. The difference is in compiling with optimizations or not, compiler option -O0 vs any other optimization option. Would this be considered a compiler/optimizer bug? Older versions of Xcode (15.4 and earlier) do not have this problem.