Fixed
Status Update
Comments
an...@seventhbeam.com <an...@seventhbeam.com> #2
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:
il...@google.com <il...@google.com> #3
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.
ap...@google.com <ap...@google.com> #4
We never supported Roboelectric. All WorkManager tests need to run as an Android instrumentation test.
il...@google.com <il...@google.com> #5
This is fixed and will be available in Navigation 1.0.0-beta02.
Description
Version used: 1.0.0-beta01
When at start destination the nav controller will consume 2 back presses before popping out of the app. If only 1 navigateUp is called, subsequent navigateTo(...) calls will result in an illegal state exception and crash the app.