Open rigamikhail27 opened 1 year ago
Hey! Got the same issue. It'd be nice to fix that. Thanks in advance!
Thanks @rigamikhail27 for raising this issue and for the clear reproduction. I see the same issue on iOS 14, and you are using the library as intended, so this is definitely something to be fixed. I've done a little investigation but so far I haven't developed any insight, but will keep you posted.
@johnpatrickmorgan any idea?)
Hi @rigamikhail27, sorry I haven't had any breakthrough. I checked older FlowStacks
versions and the issue has been present since the inception of the library. I'm afraid it might be the case that FlowStacks' approach to nesting coordinators is not compatible with SwiftUI on iOS 14, at least for push navigation (presentation seems to work as expected).
I'm considering a significant rewrite of the library to bring the API more in line with the new navigation APIs in iOS 16 (point 2 here). I believe that would allow a more robust approach to nesting coordinators. Sorry I can't offer a better solution.
Got it, thanks! Current implementation is useful, so I will better up min support version to 15🙂
Follow-up: here's an early peek at the possible rewrite: #51
Hi everybody and thanks a lot @johnpatrickmorgan for this job! I was looking chance to organise my app code with MVVMc + SwiftUI and draw a conclusion, that FlowStacks is a best solution!
Here is a code example with weird behaviour when put one Router inside other leads to popping instead of pushing and only on iOS <= 14.5. (routes.push(.second) -> pops back to .root(.main) in CoordinatingViewB)
Of course, I may use it incorrectly, that's why need your experience and waiting for it)
Thanks!