Navigate navigates into void sometimes about swiftui-router HOT 3 OPEN

So since using navigator.navigate instead of rendering a Navigate, this error doesn't happen anymore. Still a little annoying but it is a good hack at least.

from swiftui-router.

Oh, forgot to mention it. Once the app is in this state, it does that all the time. So e.g. in this example the default route should go back to "/home/root" but instead, again, navigates to /home fallback (endless loop). That's why I don't even fallback but rather go to an empty screen because of SwiftUI's optimizations.

from swiftui-router.

Hmm it's very possible you're talking about a bug I've encountered very rarely - like only three times in total. Unfortunately so far I have been unable to successfully (and consistently) reproduce it.

The one time I did caught it, however, it looked like - for whatever reason - SwiftUI decided to render the children of SwitchRoutes in reverse order. Like some weird magic optimization SwiftUI decided to perform out of nowhere. Meaning the last route would render (and perform path matching) first, instead of last. Thus resulting in the behaviour you described.

My gut tells me this is some optimization introduced in SwiftUI 3, as I don't recall experiencing this bug in SwiftUI 2. But it's hard to tell.

It is certainly worrying, and I really hope to find a method/routine to reproduce this bug consistently to further investigate it. Any help on this matter would be greatly appreciated!

So far from the top of my head potential solutions could be making a custom ViewBuilder for SwitchRoutes (lord have mercy), or work with .id() for Routes views (yuck). 😞

from swiftui-router.