Fixed
Status Update
No update yet.
Comments
se...@google.com
Your test is configured to run as a Junit test using Roboelectric.
The work-testing artifact only supports android instrumentation tests. For more information please take a look at:https://github.com/googlesamples/android-architecture-components/blob/master/WorkManagerSample/app/build.gradle#L64
The work-testing artifact only supports android instrumentation tests. For more information please take a look at:
au...@gmail.com
Hi,
thanks for your answer. I believe this has changed in the last version? as until 1.0.0-alpha11 it was possible to run a Worker in Junit test with Robolectric.
thanks for your answer. I believe this has changed in the last version? as until 1.0.0-alpha11 it was possible to run a Worker in Junit test with Robolectric.
il...@google.com
ap...@google.com
We never supported Roboelectric. All WorkManager tests need to run as an Android instrumentation test.
il...@google.com
ko...@gmail.com
yes i tested it on
Description
Navigation
Version used:
1.0.0-alpha04
Devices/Android versions reproduced on:
All
Steps to reproduce:
- Create multiple fragments with separate Toolbars. Lets Say A and B
- Move from A -> B and use NavigationUI.setupWithNavController(fragmentBToolbar, nav)
- Go back to A. Layout of fragment B is leaked forever.
Problem:
With every call
navController.addOnNavigatedListener(new NavigationUI.ToolbarOnNavigatedListener(toolbar, drawerLayout));
new listener is added to navController with hard reference to Toolbar view. And ToolbarView has reference to its parent View (fragments View). And never cleared