Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deeplinking to nested beams #553

Open
ericf-br opened this issue Jul 31, 2022 · 6 comments
Open

Deeplinking to nested beams #553

ericf-br opened this issue Jul 31, 2022 · 6 comments
Labels
question A question about usage

Comments

@ericf-br
Copy link

I can't seem to find a way to do this.

The main app has a BeamerDelegate with Locations A, B, C.
Location A is a BottomNavBar with it's own Beamer and Delegate, D, E ,F

A deep link such as myapp://myapp.com/B will work.
A deep link to myapp://myapp.com/E will NOT work because it's delegate is not the main app's delegate, so you get page not found. I can't find a way to "forward" the deep link to the bottom nav bar's BeamerDelegate.

Thoughts?

@IlyaMax
Copy link

IlyaMax commented Jul 31, 2022

@ericf-br at least there is one work around you can use: navigate to concrete tab you want with something like bloc/cubit/valuenotifier. And then navigate to concrete screen via tab beamer delegate.

@rivella50
Copy link

I handle incoming links and write them into a state object.
Then the listener decides where to navigate, and therefore you could use a nested path for directly navigating to location E, e.g. with a path '/A/E'.

@NeroThroN
Copy link

@ericf-br I've found the same issue when creating this example.

Have you other weird behaviors on your main app structure with nested navigation and BottomNavBar ?

(Don't hesitate to take a look at the example's PR to see if you have already fix some of the issues listed)

@slovnicki slovnicki added the question A question about usage label Sep 6, 2022
@slovnicki
Copy link
Owner

myapp://myapp.com/E will NOT work

This is because E is inside the A router, so A router has to be built/entered first. A route like myapp://myapp.com/A/E and having A handle all /A/* paths should do the job.

@LaysDragon
Copy link

Well the nested beamer is still a separated navigator from root beamer as I understand,I can feeling there is design conflicting between "flutter app state styles url routing" and "web url navigation",and make its hard to deal with real web url stuff.🤔

@Ashhas
Copy link

Ashhas commented Aug 30, 2023

@ericf-br were you able to figure out how to properly implement this? 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question A question about usage
Projects
None yet
Development

No branches or pull requests

7 participants