Fixed
Status Update
No update yet.
Comments
ap...@google.com
That seems quite bad :/ weird.
We have fairly large test projects which do not take anywhere close to it, maybe your code is triggering some bad code path.
Can you provide a sample or share your project with us? It is impossible to do something here unless we have a reproduction case. Might also possibly be related to your machine configuration.
We have fairly large test projects which do not take anywhere close to it, maybe your code is triggering some bad code path.
Can you provide a sample or share your project with us? It is impossible to do something here unless we have a reproduction case. Might also possibly be related to your machine configuration.
ap...@google.com
Let me see what I can do on the reproduction as I am anyways blocked on this. I will try to extract out the DB module in a new project and see if it reproduces the issue.
jb...@google.com
Attaching the sample project. When I run the project through the android studio or even command line, I see the described issue.
Try uncommenting room-compiler dependency from app's build.gradle, it does not have the issue because room compiler is not at work.
Try uncommenting room-compiler dependency from app's build.gradle, it does not have the issue because room compiler is not at work.
Description
Having just a
remember { }around calls togetBackStackEntry(route)causes new entries with the same id to use the old remember scope which can cause crashes. We should instead be telling devs to useremember(entry) { }using the entry from thecomposablefunction lambda scope as the input to theremembercalculation. This way, whenever the entry object changes, we also recompose therememberand we never get a stale entry.