Xcode

Apple now accepting Xcode 26.2 RC submissions

The OS is shutting down our app due to high memory usage. In our app, each “room” is an immersive space with a skybox. Within the room we navigate through a variety of spaces, each with its own texture to be used in the skybox material. Each time we swap out the skybox material the memory usage grows significantly. When we exit each room (immersive space), we remove the skybox (removeFromParent), assign it to nil, and have even tried to set the Texture to nil. Exiting a room doesn’t appear to release any of the allocated memory. Each time we enter a new room the memory usage climbs until we reach about 5G, by which time the app is closed by the system. Should we remove the UnlitMaterial reference in each room object as well upon exiting immersive space? We also observed that when we navigated through spaces that we’ve previously visited, the Persistent Bytes don’t grow even though we are releasing the Texture resource upon exiting a space, then re-creating the TextureResource when we enter it again. Could the

See the first message in this thread for the FB number. I've added a line that this still seems to be broken in the 26.2 beta I tested in simulator. The bug report also contains a trivial Xcode project to reproduce the problem.

I figured out the issue! I recently received a new external drive into which I setup XCode to write its Derived Data and Archives. This external drive was formatted as ExFAT. I have now reformatted the drive as Mac OS Extended (APFS was not an available option in my Disk Utility) and rebuilt the application. The updated pkg using the rebuilt and notarized application now correctly installs to /Applications. It's unfortunate that I could not find a Console log or display verbose enough information via sudo installer -verboseR detailing why the application was not being written to /Applications. Hopefully this post helps someone in a similar situation. Thank you for your time and responses.

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.

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.