xcode github

I am trying to solve an issue when converting an existing project to use Buildable Folders: Our current project have some custom file types that have specialized build rules, as described here: https://developer.apple.com/documentation/xcode/creating-build-rules-for-custom-file-types We previously added each of these file types, to the target's Compile Sources phase and everything was running well. Now we wish to move these files into a Buildable Folder, but I cannot find a way to make it work ... as only files with a specific file extensions are ever built in a Buildable Folder, and despite having a custom rule for this file type, it seems like Xcode never runs the rule. Is there some way to tell Xcode to treat specific extensions in a Buildable Folder as source extension?

I'm having a problem with Xcode 26 where a symbol bug is causing my app to crash at launch if they are running iOS 17.X This has to do with a HealthKit API that was introduced in iOS 18.1 HKQuantityType(.appleSleepingBreathingDisturbances), I use availability clauses to ensure I only support it in that version. This all worked fine with Xcode 16.4 but breaks in Xcode 26. This means ALL my users running iOS 17 will get at launch crashes if this isn't resolved in the Xcode GM seed. I'll post the code here in case I'm doing anything wrong. This, the HealthKit capability, the HealthKit Privacy - Health Share Usage Description and Privacy - Health Update Usage Description, and device/simulator on iOS 17.X are all you need to reproduce the issue. I've made a feedback too as I'm 95% sure it's a bug: FB19727966 import SwiftUI import HealthKit struct ContentView: View { var body: some View { VStack { Image(systemName: globe) .imageScale(.large) .foreground

Hi everyone! I've noticed a color rendering issue with Home Screen widgets on iOS 26: the colors displayed in widgets are inconsistent with those shown inside the app. At first, I suspected this might be caused by differences in color spaces, but even after explicitly specifying the color space for SwiftUI.Color or UIColor, the widget colors remain incorrect. Steps to reproduce: Create a new iOS project in Xcode 26 beta 6. Add a new Widget Extension target. Use the following Widget view code: struct MyWidgets: Widget { let kind: String = MyWidgets var body: some WidgetConfiguration { StaticConfiguration(kind: kind, provider: Provider()) { entry in let white = Color(.sRGB, red: 1, green: 1, blue: 1) let veryLightGray = Color(.sRGB, red: 0.96, green: 0.96, blue: 0.96) let lightGray = Color(.sRGB, red: 0.9, green: 0.9, blue: 0.9) VStack(spacing: 0) { Rectangle() .foregroundStyle(veryLightGray) // 👈 Rectangle() .foregroundStyle(lightGray) // 👈 } .containerBackground(white, for: .widget) // 👈 } .config

We are trying to track down some build failures that started happening only in our Jenkins CI environment. error: Failed to decode version info for '/Applications/Xcode.app/Contents/Developer/usr/bin/actool': The data couldn’t be read because it is missing. (stdout: ' [2025-07-30T19:21:18.479Z] [2025-07-30T19:21:18.479Z] [2025-07-30T19:21:18.479Z] [2025-07-30T19:21:18.479Z] com.apple.ibtool.version [2025-07-30T19:21:18.479Z] [2025-07-30T19:21:18.479Z] bundle-version [2025-07-30T19:21:18.479Z] 24112 [2025-07-30T19:21:18.479Z] short-bundle-version [2025-07-30T19:21:18.479Z] 26.0 [2025-07-30T19:21:18.479Z] [2025-07-30T19:21:18.479Z] [2025-07-30T19:21:18.479Z] [2025-07-30T19:21:18.479Z] ', stderr: '' Key facts we've noted: Locally I cannot reproduce the problem We did not see this problem with previous Xcode 26 betas If I remote into the machine and run build commands from the command line I cannot reproduce the problem The very first build succeeds, every build after that on this machine fails

When Xcode 26 Beta 5 compiles my XIBs into NIBs, it spits out a dependency on a class that isn't available pre-macOS 26, named _TtCC6AppKit14NSScrollPocketP33_EC3F85FAB7755D56E669206D2B17725B12BackdropView. All XIBs have a deployment target of macOS 12, so in theory this should be avoided. Even if this is a new (internal) class to macOS 26, the dependency is a problem when the developer is asking to deploy to prior versions. Has anyone else run into this regression? What could possibly be causing the XIB compiler to inject this dependency? The resulting NIBs don't load on anything prior to macOS 26.