Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
[ID: 84651]
Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. Each team will estimate work on a slightly different scale, which means the values in this field are likely only meaningful to the team that owns the Buganizer component in which the issue resides.
See Atlassian's Agile Coach for more information on how to use story points for estimation: https://www.atlassian.com/agile/project-management/estimation [ID: 746686]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
[ID: 85206]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
#1Android Studio Build: 2020.3.1 Patch 2
Kotlin version: 1.5.21
Issue:
Expected behaviour would be that each ViewModel instance should stay the same when selecting the bottomBar tabs.
In practice - the ViewModel instances change, if switching is happening very fast.
I'm not totally sure whether this is compose issue, compose-navigation issue, or Dagger Hilt issue since they all are related here.
An important note - setup in the reproducible sample is supporting multiple back stacks.
Steps to Reproduce:
1. start the project where the issue can be reproduced
2. it contains a function imitateFastNavigation(), which will simulate fast switching bottomBar destinations. Same can be done by commenting it out and fast tapping manually.
3. Open the logcat, and ensure that the viewModels are actually changing, instead of being the same.