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

[Navigation] Wrong ViewModel attached to page when NavigationCacheMode set to Required #2097

Closed
9 tasks
nickrandolph opened this issue Dec 7, 2023 · 0 comments · Fixed by #2098
Closed
9 tasks
Labels
kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification.

Comments

@nickrandolph
Copy link
Contributor

nickrandolph commented Dec 7, 2023

Current behavior

App has three pages, Page1, Page2 and Page3. Routing has Page2 as dependsOn for Page3. All pages have NavigationCacheMode set to Required

Nav sequence:
Page1, Page2, Page3, (back) Page2, (back) Page1, Page 3 (this will inject Page2 into backstack), (back) Page2
Page2 has the old viewmodel and is not refreshed to a new instance

Expected behavior

Page2 should have a new viewmodel instance

How to reproduce it (as minimally and precisely as possible)

Environment

Nuget Package:

Package Version(s):

Affected platform(s):

  • iOS
  • Android
  • WebAssembly
  • WebAssembly renders for Xamarin.Forms
  • [X ] Windows
  • Build tasks

Visual Studio:

  • 2017 (version: )
  • 2019 (version: )
  • for Mac (version: )

Relevant plugins:

  • Resharper (version: )

Anything else we need to know?

@nickrandolph nickrandolph added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification. labels Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant