Can someone help me understand the behavior of ‘NavigationStack.count’. I don’t understand how/when it’s updated. In this example, I use the count to disable back navigation. But as you can see, initially(as expected), the back button is disabled on screen 1. But when I navigate to screen 2, and then back to screen 1, the back button flashes for less than a second even though the print statement shows that count is 1 and should disable back navigation.

After realizing the lookup and editing limitations of the built-in, type-erased NavigationPath, I’m exploring an enum-based solution. With this approach, I can inspect and edit the path much easier while still combining multiple types.

I’ve stumbled upon what I think is a bug in SwiftUI, but there might be an explanation for it, which I cannot to figure out. So here’s the “bug”. Perhaps any of you know it.

I’ve noticed some weird behavior when working NavigationStack paired with a NavigationPath, and I’m wondering if it’s by design or perhaps a bug.