The purpose of the go_router for Flutter is to use declarative routes to reduce complexity, regardless of the platform you're targeting (mobile, web, desktop), handling deep linking from Android, iOS and the web while still allowing an easy-to-use developer experience.
Per @nyck33's question here, I am trying to see if deep linking with my example app appearing to be working. However, I just realized that I am unsure about what to expect with oldBucket and how to restore my authState.
I did these steps.
Initially '/' to '/login' redirected
so on the login page, click the login button, goes to '/'
on the home page, enter '/polygon' to my browser's url to go to Polygons page.
I see deep linking was attempted by go_router but, because of the authStatus initialized, I ended up going to '/login' path.
@csells, could you review and advise how to use oldBucket for this use-case?
Per @nyck33's question here, I am trying to see if deep linking with my example app appearing to be working. However, I just realized that I am unsure about what to expect with oldBucket and how to restore my authState.
I did these steps.
I see deep linking was attempted by go_router but, because of the authStatus initialized, I ended up going to '/login' path.
@csells, could you review and advise how to use oldBucket for this use-case?