xcode github

Yes，I have same problem. Any one fix the problem? Here is my sample code: struct BroadcastLiveActivityGradientLayerView: View { @Environment(.colorScheme) var colorScheme private var localImageName: String { colorScheme == .light ? icon_LiveActivity_broadcast_grid_light : icon_LiveActivity_broadcast_grid_dark } private var baseBackgroundColor: Color { colorScheme == .dark ? .black : .white } var body: some View { ZStack(alignment: .topTrailing) { baseBackgroundColor let colors = LiveActivityColor.broadcastBackgroundColors(colorScheme) LinearGradient( stops: [ .init(color: colors.last ?? .clear, location: 0.0), .init(color: colors.first ?? .clear, location: 1.0) ], startPoint: UnitPoint(x: 0.81, y: 1.29), endPoint: UnitPoint(x: 1.29, y: 0.17) ) Image(localImageName) .resizable() .aspectRatio(contentMode: .fill) .frame(width: 179, height: 149) } } }

For anyone watching the link kindly provided by Albert, a new note is probably not created: December 8, 2025 TestFlight update You can now upload apps built with Xcode 26.2 RC using the SDK for iOS 26.2 RC, iPadOS 26.2 RC, macOS 26.2 RC, tvOS 26.2 RC, visionOS 26. 2 RC, and watchOS 26.2 RC for internal testing through TestFlight. because towards the end of the following day, December 9th, observe how and external was silently inserted: December 8, 2025 TestFlight update You can now upload apps built with Xcode 26.2 RC using the SDK for iOS 26.2 RC, iPadOS 26.2 RC, macOS 26.2 RC, tvOS 26.2 RC, visionOS 26. 2 RC, and watchOS 26.2 RC for internal and external testing through TestFlight. So watch carefully the same previously dated release note for App Store to be inserted.

Hello I don't recommend trying to implement controller tracking & recasting using the controller's IMU data. ARKit in visionOS 26 has support for tracking 6DOF pose of PSVR2 controllers. Apple publishes a Unity plugin that bridges the native GameController + ARKit support for discovering and tracking spatial game controllers into Unity. See Apple.SpatialAccessory in the Apple unity plugins Github.

Still no luck, unfortunately. OSX version is 15.7.2. I created a new user account, and as such, needed to add the Developer ID Application and Developer ID Installer certificates for our organization to XCode. After building the application, I had it notarized using XCode's Organizer window via the Direct Distribution option. Unfortunately, the package installer still wrote a zero-byte application to the /Application folder. I verified the installer had the correct Payload by extracting and decompressing the package data. Quite the head scratcher. Thank you for any insight.

Thanks for providing some code. I was able to reproduce the problem you have described here. 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.

Thank you for your response and for taking the time to read the Technical Note. I believe you have now realized that Universal Links function consistently well, but there could be several reasons for their behavior deviating from expectations: When encountering issues related to Apple-app-site-association files and associated domains, particularly when they function correctly on the first attempt but fail on subsequent attempts within the same tab, several potential security and configuration factors could be at play: JavaScript Logic Errors: Although you mentioned that the code execution is identical, race conditions or state mismanagement within your JavaScript could lead to differing outcomes on successive runs. Please verify for such possibilities. Error Handling and Logs: Enhance error handling surrounding the associated domain validation logic and ensure comprehensive logging to capture any discrepancies during the second invocation. By systematically examining these areas, you should be able to identif

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.

Thanks for the post and thank you for bringing this issue to our attention. Indeed, this is a known problem where SwiftUI control will need to resize a window with a NavigationSplitView generates Invalid view geometry warnings in Xcode. The issue is currently being investigated. If you would like to be notified when the fix is implemented and Xcode ceases to issue these warnings, we recommend filing a bug report. The warning looks something like this: Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to.. In the meantime, please be advised that the engineering team is actively addressing the warning issue. If you want to file a bug please post the FB number h