I am currently developing a macOS app that can show system HUDs in the Notch Till Sequoia I used to kill the OSDUIHelper process (which displays the default macOS Volume and Brightness control HUDs) - and replaced it with my app's HUDs But, it is not working on macOS Tahoe anymore as the OSDUIHelper process is no longer there due to the UI changes Has the process been renamed - or is there any other way to kill the process?

Hi so i have a given project where I am trying to use components within the PhotosUI Framework with Xcode26 and Xcode26.0.1 Just for reference here is an attached screenshot This sample code compiled successfully with xcode16.4 and was in production. There is no change in the pbxproj file , all the build settings have remained the same. Attaching it for reference. project.pbxproj.txt While showing declarations of PHPickerViewControllerDelegate i get two options which is the same as in Xcode16.4 while browsing online found this reddit thread which is very similar https://www.reddit.com/r/Xcode/comments/1nkku20/my_project_wont_compile_after_xcode_26_update_due/ Pls help :)

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

I have an early-stage framework project where the Xcode project directory is named HXiMateSDK. When I switched to a new Mac device, the framework compiled using the newly installed version of Xcode failed to compile in the old version of Xcode on the old machine. My clients might use my framework in different Xcode versions, so I need to resolve this issue. STEPS TO REPRODUCE The built product HXiMateSDK.framework from the new machine A, which was compiled using the latest Xcode version 26.0.1 (17A400). When creating a new project justTestNew on the new machine A using the latest Xcode version 26.0.1 (17A400), calling the method getSDKVersion from the HXiMateSDK.framework compiles successfully. When creating a new project justTestOldEnv on the old machine B using Xcode 13.2.1 (13C100), calling the method getSDKVersion from the HXiMateSDK.framework results in a compilation failure.

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.

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.

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.

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

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.

Hi, It seems that the files that are added to a targets compilation list cannot be hardcoded. If the file doesn't exist in the file system then it cannot be added to the compilation list. If this is true then how are autogenerated files handled in Xcode. I want to autogenerate some code but since I can't add those files in to the project, the first compilation (that generates those files) always fails. This is especially problem in CI. How is I should handle this in Xcode

SceneDelegate's sceneWillEnterForeground and sceneDidEnterBackground methods are not called when app is moved to the background and back. It happens when Stage Manager is enabled and application is moved to the background using App Switcher (double tap on the home button). Otherwise methods are called. Started to reproduce since iOS26. Is not reproducible on iOS18.

I'm facing a build failure after migrating my project to Xcode 26. The issue appears to be related to the redefinition of some core system types. The compiler errors point to a failure to locate the original type definitions, suggesting they've been moved or renamed. Specifically, the build log contains these errors: ../arm64-apple-ios.private.swiftinterface:653:11: Cannot find type '_sys_select' in scope ../arm64-apple-ios.private.swiftinterface:130:33: Cannot find type 'netinet_in' in scope I've observed that the types are being mapped as follows: netinet_in.in_addr_t -> _DarwinFoundation2.in_addr_t _sys_select.fd_set -> _DarwinFoundation2.fd_set I'm looking for guidance on the recommended way to resolve these API changes. How should I handle these type redefinitions in Xcode 26 to ensure my project builds correctly? Any insights would be greatly appreciated. Thank you.

Hi everyone, Since updating to Xcode 26, I’ve been running into an issue with the new ChatGPT integration inside Xcode. Even though I have an active ChatGPT Plus subscription (GPT-4 or GPT-5) and I’m signed in to my OpenAI account, Xcode doesn’t seem to recognize my paid plan. After reaching the free usage limit, I get the following message: “Over daily limit. ChatGPT in Xcode will be unavailable for up to 24 hours. For higher limits, sign in with a paid ChatGPT account or upgrade to ChatGPT Plus.” The issue is that I am already logged in with my ChatGPT Plus account, and everything works fine on the ChatGPT web app — but inside Xcode, it keeps treating me as a free user. Here’s what I’ve tried so far: • Signing out and back into ChatGPT from within Xcode • Restarting Xcode and macOS • Verifying that I’m logged in to ChatGPT in Safari • Updating both macOS and Xcode to the latest versions None of these steps have resolved the issue. It seems like Xcode isn’t syncing properly with OpenAI authentication, and therefore it applies the free-tier limits even for paid accounts. Has anyone else encountered this problem? Is there any way to force Xcode to reauthenticate with OpenAI or link it properly to a ChatGPT Plus account? System setup: • Mac mini (Apple M2, 16 GB RAM) • macOS Tahoe 26.0.1 • Xcode Version 26.0.1 (17A400) Here’s the error message I’m seeing:

When I use the method provided in the document https://developer.apple.com/documentation/passkit/pkpasslibrary/activate(_:activationdata:completion:)?changes=_1__4,_1__4 to verify a card that has been added to Apple Wallet, I get an error code: 500 unknown error How can I troubleshoot the problem?

I've recently switched from using Xcode 15 under Ventura to using Xcode 26 under Sequoia on an Intel-CPU Mac. This is a macOS project that uses a legacy build location, and the sources are C++ and Objective-C. For every source being compiled, I get a clang warning "no such include directory" for these 4 directories: $BUILD_DIR/Debug/include $BUILD_DIR/SBEngineV4.build/Debug/V4 Dual SBEngine.build/DerivedSources-normal/x86_64 $BUILD_DIR/SBEngineV4.build/Debug/V4 Dual SBEngine.build/DerivedSources/x86_64 $BUILD_DIR/SBEngineV4.build/Debug/V4 Dual SBEngine.build/DerivedSources I can't figure out where it's getting those directories. I added a Run Script build phase that says echo $HEADER_SEARCH_PATHS, and the first path that reports is the $BUILD_DIR/Debug/include path, yet I don't see that when I look at the header search paths in the target build settings. I tried deleting all the derived data. I tried Xcode 26.0.1 and 26.1 beta 2.

Hello there! In one of my apps, I noticed that the view hierarchy debugger isn't working anymore inside Xcode 26. So I created a new project, to see if it's just my project or Xcode. With the new project, it didn't happen. What can I do here? I already reported that issue. Here is the id of it: FB20605681

In my app target Foo, I have a dependency on package Bar. Bar itself have a dependency on another package Other. In my test target FooTests, I have a dependency on package BarTestsHelpers. BarTestsHelpers depends on Bar. When compiling test target FooTests, I get the following unexpected warning in Xcode 26 only: 'Bar' is missing a dependency on 'Other' because dependency scan of Swift module 'Bar' discovered a dependency on 'Other' I can see this is being discussed here as well without a solution. I filled a feedback with a sample project here: FB20602885 It seems that we can remove the warning by explicitly adding the dependency Other on BarTestHelpers. But this shouldn't be needed as BarTestHelpers doesn't use nor know about Other, it only needs it as part of its dependency on Bar.