Fixed
Status Update
No update yet.
Comments
ra...@google.com
Information redacted by Android Beta Feedback.
ca...@careem.com
Thank you for reporting this issue. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
ra...@google.com
Upon more testing myself, it looks like an additional home button press is being invoked when swiping home. You can verify this within Nova Launcher by setting a "Home button" action in Nova Settings > Gestures and inputs. Observe that the additional action you set will also be activated occasionally when you swipe home. In the attached screen recording, I've set the extra home button action to open the Google Assistant.
Tapping the screen during the return-to-home transition on the past couple Android releases would cancel the animation and you'd instantly end up on your home screen. It looks like that's what is happening here as well -- the extra invocation of the home button press is cancelling the transition animation (and with Nova, running the action you set if any). I couldn't say whether or not that's related to the content flat out not appearing though.
https://drive.google.com/file/d/1_pmlVTs78SbuiTBatk4Q_KDx88nCrKoX/view?usp=drive_web (screen-20230413-004652.mp4)
Tapping the screen during the return-to-home transition on the past couple Android releases would cancel the animation and you'd instantly end up on your home screen. It looks like that's what is happening here as well -- the extra invocation of the home button press is cancelling the transition animation (and with Nova, running the action you set if any). I couldn't say whether or not that's related to the content flat out not appearing though.
Description
I have created a Worker and a test class running it, but the doWork method is not called.
I have tried to debug the issue and the work is not executed as the constructor of `TestWorkManagerImpl` creates a list of Schedulers with one `null` Scheduler. due to this the Schedulers.schedule method throws a null pointer exception.
Here is the stacktrace from the exception:
androidx.work.impl.Schedulers.schedule(Schedulers.java:91)
androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:131)
androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:92)
androidx.work.testing.TestWorkManagerImpl$1.executeOnBackgroundThread(TestWorkManagerImpl.java:63)
androidx.work.impl.WorkContinuationImpl.enqueue(WorkContinuationImpl.java:185)
androidx.work.impl.WorkManagerImpl.enqueue(WorkManagerImpl.java:305)
androidx.work.WorkManager.enqueue(WorkManager.java:180)
com.example.carlo.myapplication.testWorker() <--- where WorkManager.getInstance().enqueue(request) is called
I have also created a project with one failing test.
I am using WorkManager 1.0.0-beta01
Please let me know if you need more information