-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[BUG] BindingContext cleared when performing absolute navigation #3113
Comments
@renduNP is this issue specific to Android? Prism shouldn't have any platform specific behaviors here. |
@dansiegel I work with @renduNP and assisted in the investigation on this issue. The best example we were able to recreate in the reproduction sample was when navigating absolutely from the |
@dansiegel - As per last communication sent, understand this is particularly tricky to fix because it is due to some platform specific behaviour. |
Description
Our Developers have observed an issue that affects Android while using absolute navigation.
E.g. When performing absolute navigation from PageA to a TabbedPage, it appears that PageA's BindingContext is cleared before PageA is removed from UI and the navigation completes.
This results in any controls that are bound to PageA's BindingContext will reset/update causing the UI of PageA to appear incorrectly until the navigation completes. It also appears that the complexity of the tabs being navigated to will affect the time taken for navigation to complete, which can cause PageA to remain visible for several seconds with incorrect UI.
We have observed this issue on version 9.0.436-pre, we are unaware of a version where this issue does not occur.
Steps to Reproduce
See Sample app to reproduce the issue here -
PrismMauiApp2.zip
Platform with bug
.NET MAUI
Affected platforms
Android
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: