IllegalStateException when Screen with LifecycleObserver is popped on start [184664896]

Fixed

Bug

Status Update

No update yet.

Description

mi...@gmail.com

created issue #1

Apr 7, 2021 05:34PM

Library version used: 1.0.0-rc01(same for beta01) Devices/Android versions reproduced on: Pixel 5/11 Android Auto version reproduced on: 6.1.610544-release

I have a Screen that observes a LiveData, and pops itself when some condition meets. The observer will run on start, so the screen will also be popped on start.

class SomeScreen(carContext: CarContext) : Screen(carContext) {
    private val someLiveData = ...
        
    init {
        someLiveData.observe(this) {
            if (someCondition) {
                screenManager.pop()
            }
        }
    }

    ...
}

The above code works well. However, when I add a LifecycleObserver to the screen's lifecycle, the app crashes.

class SomeScreen(carContext: CarContext) : Screen(carContext) {
    private val someLiveData = ...
        
    init {
        lifecycle.addObserver(object : DefaultLifecycleObserver {}) // <- this change

        someLiveData.observe(this) {
            if (someCondition) {
                screenManager.pop()
            }
        }
    }

    ...
}

Stack trace:

java.lang.RuntimeException: java.lang.IllegalStateException: no event up from DESTROYED
    at androidx.car.app.utils.RemoteUtils.lambda$dispatchHostCall$0(RemoteUtils.java:121)
    at androidx.car.app.utils.-$$Lambda$RemoteUtils$hqdRHUgQFt6LDam0B8zarqtlYt0.run(Unknown Source:6)
    at android.os.Handler.handleCallback(Handler.java:938)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:223)
    at android.app.ActivityThread.main(ActivityThread.java:7660)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
 Caused by: java.lang.IllegalStateException: no event up from DESTROYED
    at androidx.lifecycle.LifecycleRegistry.forwardPass(LifecycleRegistry.java:263)
    at androidx.lifecycle.LifecycleRegistry.sync(LifecycleRegistry.java:307)
    at androidx.lifecycle.LifecycleRegistry.moveToState(LifecycleRegistry.java:148)
    at androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent(LifecycleRegistry.java:134)
    at androidx.car.app.Screen.lambda$dispatchLifecycleEvent$1$Screen(Screen.java:321)
    at androidx.car.app.-$$Lambda$Screen$QLPRkJyaz7mYtbbcK-oQ2Y-L480.run(Unknown Source:4)
    at androidx.car.app.utils.ThreadUtils.runOnMain(ThreadUtils.java:39)
    at androidx.car.app.Screen.dispatchLifecycleEvent(Screen.java:315)
    at androidx.car.app.ScreenManager.pushInternal(ScreenManager.java:260)
    at androidx.car.app.ScreenManager.push(ScreenManager.java:80)

Comments

ro...@google.com <ro...@google.com> Apr 12, 2021 04:34PM

Assigned to sh...@google.com.

sh...@google.com <sh...@google.com> Apr 13, 2021 06:12AM

Accepted by sh...@google.com.

ap...@google.com <ap...@google.com> #2Apr 13, 2021 07:04PM

I have updated AS to version 4.1.3 and the android emulator to version 30.5.3.0. Now I can't use the emulator anymore. I have Mojave OS installed and I confirm the same message described in previous post. The file does not exist in the file system.

sh...@google.com <sh...@google.com> #3Apr 13, 2021 07:25PM

Marked as fixed.

As a workaround, I was able to successfully downgrade android emulator to 28.

See: https://stackoverflow.com/questions/49120854/how-to-downgrade-android-emulator

I downloaded 28.0.25.0 (build_id 5395263) from here:

https://dl.google.com/android/repository/emulator-darwin-5395263.zip

I deleted everything EXCEPT package.xml from

$HOME/Library/Android/sdk/emulator/

and replaced them with the contents of the extracted zip file.

Finally, make sure your AVD system image is NOT running api 30.

sdkmanager "system-images;android-27;google_apis_playstore;x86"

System images higher than api 29 are using a kernel format that the older emulator cannot understand.

Here's a workaround script you can try:

cd ~
mkdir emulator_downgrade
cd emulator_downgrade
wget https://dl.google.com/android/repository/emulator-darwin-5395263.zip
unzip emulator-darwin-5395263.zip
mv ~/Library/Android/sdk/emulator ~/Library/Android/sdk/previous-emulator
mv emulator ~/Library/Android/sdk/emulator
cp ~/Library/Android/sdk/previous-emulator/package.xml 
~/Library/Android/sdk/emulator/package.xml
cd ~
~/Library/Android/sdk/emulator/emulator -version
~/Library/Android/sdk/emulator/emulator -list-avds

ji...@gmail.com <ji...@gmail.com> #4Feb 17, 2022 05:56AM

Thank you for the downgrade explanation. If you want to use a more recent emulator 30.1.5 the build number is 6855416. I believe you can use this build with API 30 images without issues.

Issue 184664896