I can confirm this is still the behaviour on iOS 16. Its a shame because popover bubbles are very common on iOS for providing users with tutorials on how to use the app. This should be fixed. If you wanted to show a sheet instead of a popover on iPhone, you could easily just create a view modifier that does the existing behaviour.

This is because your observable object is being used by both a view that is hosting a navigation view, and one of the children being presented by a navigation view. So when the child updates the observable object, it causes the parent to reload. Which in turn causes its navigation stack to be drawn from scratch as well. the solution is to decouple the parent from the observable object. So it’s not reloading each time it changes. A technique I use is to wrap an observable object inside another. What this does it it allows me to inject them via @EnvironmentObject, without causing the views to reload unnecessarily. class Dependency<T: ObservableObject>: ObservableObject { let observable: T init(observable: T) { self.observable = observable } }

I seem to have solved the issue. Purged Xcode from my machine again. Including all caches. Deleted the contents of the /Library/Developer folder restarted my machine installed command line tools with Xcode-select --install redownloaded Xcode I think the PrivateFrameworks folder inside of /Library/Developer/ was the culprit. Its last modified time was when I installed Xcode 14 beta, not the last time I reinstalled Xcode 13.4.1 I imagine some of the stuff the simulator runtime relies on was corrupted.

I figured out what was wrong with it: this was what I was doing: for await _ in NotificationCenter.default.notifications(named: UIDevice.orientationDidChangeNotification, object: self) { print("orientation changed") // This would never fire } I changed it to: for await _ in NotificationCenter.default.notifications(named: UIDevice.orientationDidChangeNotification) { print("orientation changed") // This works } I guess I misunderstood what that object param was used for.

I honestly have not been able to get this to work either. It would be nice to see a demo of it in action.

Same issue here. A partial solution is to add the sign in with apple button to a navigation view. But if you log out and pop back to the login screen, it seems to happen again.

Having the same issue with one of our own swift packages. Works fine on intel Macs. Does not work on apple silicon Macs.

I have this issue as well. Xcode 12.3 is completely unusable.