You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a flutter app with nested delegates i observe that the nested delegate doesn't rebuild itself by deeplink to already opening app.
Short steps to reproduce on android:
have nested beamer delegates
simulate a deeplink action by the command adb -s shell am start -a android.intent.action.VIEW -c android.intent.category.BROWSABLE -d "<deeplink-path-to-second-beamer-delegate>"
once forward to app by the deeplink, you would see only the first screen in the first beamer delegate is rendered but the beaming history in second delegate now have new record but doesn't get rendered.
For a flutter app with nested delegates i observe that the nested delegate doesn't rebuild itself by deeplink to already opening app.
Short steps to reproduce on android:
adb -s shell am start -a android.intent.action.VIEW -c android.intent.category.BROWSABLE -d "<deeplink-path-to-second-beamer-delegate>"
After i traced the code, i found the
rebuild
flag in following code is always false. Once update to respect the rebuild parameter, the second navigator get re-rendered and the screen is correctly shown.https://github.com/slovnicki/beamer/blob/master/package/lib/src/beamer_delegate.dart#L1068
@slovnicki
Wander if there are any concern with the hard-code rebuild flag ?
The text was updated successfully, but these errors were encountered: