Status Update
No update yet.
Comments
ra...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used - Device Make, Model, Android OS Version
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen record of the issue, for clarity
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Note: Please upload the files to google drive and share the folder to
en...@gmail.com
Devices: samsung, realme, xiaomi, OPPO, motorola, LGE,
I don't know how to write code reproducing issues in Android framework, unless you explain what does "no event down from INITIALIZED" mean. Then maybe I can prepare a piece of code that doesn't "event down from INITIALIZED". Until then - sorry.
Also - this error doesn't ever show on the device it is just logged to crashlytics, so there's now way to capture anything "after reproducing the issue".
[Deleted User] <[Deleted User]>
That particular error means that you are attempting to move the Lifecycle to DESTROYED before it was actually ever moved to CREATED. It was never actually supposed to be supported, but there was a bug in Lifecycle that made it so it only failed if there was an Observer on the Lifecycle, but it was fixed in
Description
Component used: androidx.work:work-runtime AND androidx.work:work-runtime-ktx Version used: 2.5.0 and 2.7. Devices/Android versions reproduced on: Pixel 4 XL API S (Emulator from Android studio)
Simply adding the dependency of work manager runtime to a sample app (see attached) and targeting API S with
triggers the following runtime error when run on a Pixel 4 emulator with API S
2021-02-22 18:06:21.069 28402-28424/? E/AndroidRuntime: FATAL EXCEPTION: pool-3-thread-1 Process: com.example.myapplication, PID: 28402 java.lang.IllegalArgumentException: com.example.myapplication: Targeting S+ (version 10000 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent. Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles. at android.app.PendingIntent.checkFlags(PendingIntent.java:367) at android.app.PendingIntent.getBroadcastAsUser(PendingIntent.java:640) at android.app.PendingIntent.getBroadcast(PendingIntent.java:626) at androidx.work.impl.utils.ForceStopRunnable.getPendingIntent(ForceStopRunnable.java:273) at androidx.work.impl.utils.ForceStopRunnable.isForceStopped(ForceStopRunnable.java:151) at androidx.work.impl.utils.ForceStopRunnable.forceStopRunnable(ForceStopRunnable.java:171) at androidx.work.impl.utils.ForceStopRunnable.run(ForceStopRunnable.java:102) at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:920)Same app targeting API 30 works well even on Pixel 4 with API S.
Thank you for your work.
+Enea