We have filed feedback FB16424982. For anyone suffering from this regression, please consider filing a Feedback Assistant report referencing that identifier, as it will help bring attention to the problem. There is further discussion about the impact of this issue at https://github.com/orgs/skiptools/discussions/263.

This has broken the preview process for all Skip customers (see this discussion for a representative complaint). We have been guarding against ENABLE_PREVIEWS when running our tooling from the Xcode build script, and when that broke in Xcode 16 without warning, everyone's SwiftUI previews went bonkers. Surely there must be some way to prevent running a build script for the preview execution environment? Couldn't there just be a checkbox option to disable running a script when in a preview context? The "Use Legacy Previews Execution" option is not a solution because it will reset on the next Xcode upgrade – again breaking everyone's project without warning.

Are you invoking safeAddExercice asynchronously? If so, the EnvironmentObjects may not be set at the time the callback is applied because it is not happening during the lifecycle of the view. You could instead pass the environment object at the point when you schedule the exercise, thereby guaranteeing that the object will be available. E.g.: var body: some View { 		Button("Add Exercise") { 				let subman = self.subscriptionManager 				DispachQueue.main.async { 						safeAddExercice(subman) 				} 		} } func safeAddExercice(_ subman: SubscriptionManager) { 		// operate on subman rather than self.subscriptionManager }

FWIW, I am also seeing this crash with a multi-color image: "xmark.octagon.fill"