Status Update
No update yet.
Comments
cc...@google.com
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
ap...@google.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".
ap...@google.com
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
ap...@google.com
cc...@google.com
cc...@google.com
I mean it was fixed to throw the error in Lifecycle 2.5. It was always supposed to be an error.
ca...@google.com
Whoa! That's some info!
Now - how can I, having this error message and error stack, discover WHAT exactly is causing this error?
Because, you know, I don't really create thingies having their own lifecycle...
ap...@google.com
Well from the stack, your Activity is being started and the fragment is getting destroyed.
So there is some fragment that is added to your activity that is being removed before it's Lifecycle goes to CREATED.
cc...@google.com
java.lang.IllegalStateException: The content of the adapter has changed but ListView did not receive a notification. Make sure the content of your adapter is not modified from a background thread, but only from the UI thread. Make sure your adapter calls notifyDataSetChanged() when its content changes. [in ListView(2131230928, class android.widget.ListView) with Adapter(class com.students.post.Post_Fragment$Post_listAdapter)]
ap...@google.com
The LifecycleOwner is indeed available from the LifecycleRegistry so we can add that as part of the message so you know which component it is referring to.
ap...@google.com
ap...@google.com
Branch: androidx-main
commit e7dfcd2e09ee1dd3589fbd548f50617a8f1c1356
Author: sanura <sanura@google.com>
Date: Thu Oct 13 03:07:32 2022
Update LifecycleRegistry.moveToState() error message
Include the name of the component in the error
message for LifecycleRegistry.moveToState() to
better help developers debug which component is
trying to do an illegal state movement.
RelNote: "`LifecycleRegistry.moveToState()` now
includes more helpful error messaging that informs
developers of the component causing the error."
Test: moveInitializedToDestroyed update
Bug: 244910446
Change-Id: Idf4b23476f809e6c6ff2361d9e864653c90fea2a
M lifecycle/lifecycle-runtime/src/main/java/androidx/lifecycle/LifecycleRegistry.java
M lifecycle/lifecycle-runtime/src/test/java/androidx/lifecycle/LifecycleRegistryTest.java
ap...@google.com
ap...@google.com
This has been fixed internally and will be available in Lifecycle 2.6.0-alpha03
cc...@google.com
cc...@google.com
ap...@google.com
The following release(s) address this bug:
androidx.lifecycle:lifecycle-runtime:2.6.0-alpha03
ap...@google.com
Fatal Exception: java.lang.IllegalStateException: no event down from INITIALIZED in component d{7f1b10e} (0b387363-3c6b-4f7d-af8f-22ebafc87084 id=0x7f0a0302 tag=a::)
ap...@google.com
Re d is in your app, following the 'You can identify your Fragment' section in the
ap...@google.com
ap...@google.com
androidx.lifecycle:lifecycle-runtime:2.6.0-alpha03
androidx.navigation:navigation-fragment-ktx:2.5.3
androidx.navigation:navigation-ui-ktx:2.5.3
and got crash:
java.lang.RuntimeException: Unable to destroy activity {<package name hidden by me>.MainActivity}: java.lang.IllegalStateException: no event down from INITIALIZED in component androidx.navigation.NavBackStackEntry
with reason:
Caused by: java.lang.IllegalStateException: no event down from INITIALIZED in component androidx.navigation.NavBackStackEntry
(I see that issue is connected with NavBackStackEntry thanks update to :lifecycle-runtime:2.6.0-alpha03)
In my MainActivity there is NavHostFragment with NavController and queue of NavBackStackEntries inside.
When I navigate from Acitivity to some fragment using code below:
Log.i("showSomeFragment","state just before navigate: ${findNavController().currentBackStackEntry?.lifecycle?.currentState}")
findNavController().navigate(
MainNavgraphDirections.actionShowSomeFragment(...)
)
Log shows that NavBackStackEntry's lifecycle's is in state RESUMED, but in target fragment's onCreate (after navigation)
NavBackStackEntry's lifecycle's is in state INITIALIZED
Therefore, when I minimize app being on that fragment - app crashes, because I go from INITIALIZED to DESTROYED state (skipping other states).
When I navigate similarly between fragments (using findNavController().navigate in fragment, not in activity) ->
NavBackStackEntry's lifecycle's state is in state RESUMED in target's fragment onCreate an there is no crash after minimize.
Do I don't understand something/do you have any hints for that, or there is bug in navigation library?
For clarity: Yes, I understand that when we go from INITIALIZED directly to DESTROYED state - error SHOULD be thrown
ap...@google.com
ap...@google.com
Re
ap...@google.com
Fatal Exception: java.lang.RuntimeException: Unable to destroy activity {path to MainActivity}: java.lang.IllegalStateException: no event down from INITIALIZED
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:5253)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:5282)
at android.app.servertransaction.DestroyActivityItem.execute(DestroyActivityItem.java:44)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2146)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:236)
at android.app.ActivityThread.main(ActivityThread.java:8057)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:656)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)
ap...@google.com
Re
Description
Currently min API 30 due to using perfetto trace_processor_shell binary from Q platform build.
Switch to unbundled perfetto (at least on old devices) and trace_processor_shell built from github repo. Currently this is blocked on documentation for binary stripping (https://groups.google.com/a/google.com/g/perfetto-dev/c/vRHKg4Cjpok )