Tested on iPhone 14 Pro and iPhone 17 physical devices running iOS 26.2, both keep state intact and correctly increment with each display of the alert. Most teammates and myself see the loss of state behavior only on iPhone 17 (iOS 26.2) simulator and not other 17 variants or older sims. The desire of LibraryView, inside a Swift package linked as a dependency, is to show a sheet when tapped without concern about how the app is using it within its view layout (ContentView in the example). Another example could be a package that has a public AccountView that when tapped shows a private account settings view. Allowing app to display the AccountView where they want without having to know internals for displaying the settings view.

@lionelng thanks for the added context! Ya that's what we are seeing as well, having the VStack alters the behavior. Are you only seeing that state loss on the simulator or also on device?

Thanks for the help on this! Xcode Version 26.2 (17C52), issue seen on iPhone 17, iOS 26.2 simulator. presentedCount was added to highlight the issue, but main concern is that the alert automatically dismisses the first time it is shown (it's hard to tell in the video, so presentedCount was added to make it more visually apparent). Changing the ViewWithAlert properties to Binding doesn't seem to fix the alert dismissal issue. Sample Xcode project: https://drive.google.com/file/d/10S5_xdl_RZeUVSlqfCrgzIGeBFjLjRyb/view?usp=sharing

@DTS Engineer @DTS Engineer Following up on this, tested on the iPhone 17 iOS 26.1 simulator and see the same issue. Can't reproduce on any 16 simulators. Seems like a change in behavior with that version of simulator. Concern is that this behavior starts showing on device.

Thanks for chiming in @lucasgladding! The package dependency is actually the code that we are working on. We want the integration point to be simple within the apps that uses our package. It's true that moving the sheet up in the view layout does correct the behavior but that complicates the app side integration. Since it seems to be new behavior, and currently only reproducible on certain simulators, it feels like a bug. A feedback request (FB21697975) was submitted through Feedback Assistant to Apple. In our use case, the alert is a sign out confirmation alert, so having it auto dismiss creates a bad user experience and would be problematic if it started happening on devices