Fixed
Status Update
No update yet.
Comments
il...@google.com
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.
il...@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.
ap...@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
Fragments do not stop you from running both Transitions and Animations at the same time.
Combining both of them on the same Fragment can result in unexpected visual behavior such as the transition and animation blending in unusual ways.
Regardless of which one you choose, there is a way to execute all of the visual effects possible with one that you can do with both (only transitions can do shared elements), so having them together is not needed.
If you set a transition on the fragment itself, it should override whatever animation is set on the transaction.