Hello, I’m increasingly frustrated with the recent issues in iOS 18 and Xcode 16. The navigation problems in iOS 18 are a mess, and the constant crashing of SwiftUI previews in Xcode 16 is crippling my workflow. The suggested fixes haven’t helped, and this is seriously affecting my productivity. Please address these issues urgently, as they’re making it difficult to get any work done with Xcode.

Hi again. Even after trying different workarounds, including going back to the outdated NavigationView, I’m still facing light/dark mode switches in some other parts of the app where dark mode is being used. This is beyond frustrating. As a developer, it’s incredibly disheartening to have zero control over such fundamental aspects of the UI. These aren’t minor bugs—these are core features that should just work. It’s baffling that something so basic wasn’t caught before release. SwiftUI was supposed to streamline development, but with every major update, it feels like we're just trading one set of problems for another. It's exhausting to constantly battle with issues that shouldn’t even exist, especially when there’s no clear path to a solution. I really hope Apple gets its act together and sorts this out. We’re trying to build quality apps here, but right now, SwiftUI is making that nearly impossible.

Hi everyone, I'm also experiencing the double-push issue with NavigationLink in iOS 18, especially when used within a TabView. This bug has been incredibly frustrating, as it disrupts the user experience significantly. As a workaround, I've reverted to using the old-style NavigationLink with a destination and label, which thankfully seems to avoid the issue, but it's far from an ideal solution. Is there any update or a way to track the status of this bug? It would be great to know if Apple is working on a fix. Thanks, Ruben

Hey everyone, I've also run into this bug, and as a temporary fix, I've reverted to using NavigationView, which, as we know, is deprecated and not an ideal long-term solution. Is there any way to monitor the progress of this bug being addressed? Thanks, Ruben