I’m surprised this is framed as “missing functionality” rather than a regression. First, being able to suppress a miniplayer (a use case this API appears tailor-made for) when appropriate is an incredibly reasonable expectation. Second, it worked as OP describes in 26.0, including the betas I tested. Adopting the new API to align with the platform design language, only to see this change/breakage in the first dot release, is disappointing from a developer-experience standpoint

Same: FB20425139 IMHO, this is a serious regression in 26.1

Additional info: The symbolic breakpoints are not needed to understand this. Launching the app from a home screen widget doesn't even execute my App's body until the app is foregrounded. In 18.3 and earlier it did. Since the .backgroundTask modifier is applied to the WindowGroup (inside the body), we're in trouble re: making the registrations happen during launch. @DTS Engineer Can you please raise the visibility of the issue outside the CoreOS team so the SwiftUI folks get involved?