Open terekhovyes opened 1 year ago
did you find a solution?
@Bagmet-Denis unfortunately, no! It was a little project, so "solved" the problem by switching to go-router. Much harder to make navigation code well structured and easy to understand. But didn't face issues like this.
Describe the bug It looks like beamer ignores
beamBackOnPop: true
flag for iOS swipe-back transition and always shows "upward" page.I use
beamToNamed
withbeamBackOnPop: true
flag on iOS to open pages. To go back I use standard iOS back-swipe gesture, which, you know, allows to see previous page where we are going to. The problem is instead of seeing correct "beam-back" page where I'm really going to - I see "pop" page where I would go if I didn't setbeamBackOnPop
flag. When swipe is finished - screen blinks and replaces "pop" page with correct "beam-back" page.Beamer version: 1.5.3
Code to reproduce bug:
To Reproduce
Expected behavior On step 3 - I see "Movie 1" page which I'm going to by saying it to Beamer with "beamBackOnPop" flag
Screenshots
Smartphone:
Additional context My idea was to test how Beamer can handle situation when navigation graph have loops - I call it "infinite navigation case". I see that I can just build long url (like /movie1/movie2/movie10/movie5/movie7) - but don't know if
RoutesLocationBuilder
allows to do it.beamBackOnPop
looked like solution for this situation - but I stuck with bug described above :)