StartupException in ProcessLifecycleInitializer [216490724]

Fixed

Bug

Status Update

No update yet.

Description

ih...@gmail.com

created issue #1

Jan 26, 2022 11:30PM

Component used: lifecycle-process

Version used: 2.5.0-alpha01

Devices/Android versions reproduced on: Android 11 on Xiaomi Mi 8

Description: After update lifecycle component to version 2.5.0-alpha01 I received error on application launch:

E/AndroidRuntime: FATAL EXCEPTION: main
    Process: ru.omnidesk.android.app.debug, PID: 28421
    java.lang.RuntimeException: Unable to get provider androidx.startup.InitializationProvider: androidx.startup.StartupException: androidx.startup.StartupException: java.lang.IllegalStateException: ProcessLifecycleInitializer cannot be initialized lazily. 
    Please ensure that you have: 
    <meta-data
        android:name='androidx.lifecycle.ProcessLifecycleInitializer' 
        android:value='androidx.startup' /> 
    under InitializationProvider in your AndroidManifest.xml
        at android.app.ActivityThread.installProvider(ActivityThread.java:7251)
        at android.app.ActivityThread.installContentProviders(ActivityThread.java:6787)
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6704)
        at android.app.ActivityThread.access$1300(ActivityThread.java:237)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:223)
        at android.app.ActivityThread.main(ActivityThread.java:7664)
        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)

I didn't make any other changes to the project, and in manifest I have meta-data block. But I investigated this and think this is due to EmojiCompatInitializer from emoji2 witch call:

  LifecycleOwner lifecycleOwner = appInitializer
                .initializeComponent(ProcessLifecycleInitializer.class);

in method delayUntilFirstResume. I hope my thoughts will help in a speedy solution to the problem.

Comments

il...@google.com <il...@google.com> #2Jan 26, 2022 11:34PM

Yigit, do you have time to fix it?

reemission of the same liveData is racy

ih...@gmail.com <ih...@gmail.com> #3Jan 26, 2022 11:51PM

yea i'll take it.

lifecycle-process-crash.zip

106 KB

Download

b9...@gmail.com <b9...@gmail.com> #4Jan 27, 2022 09:11PM

Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.

ih...@gmail.com <ih...@gmail.com> #5Jan 27, 2022 09:22PM

just emitting same live data reproduces the issue.

@Test
fun raceTest() {
val subLiveData = MutableLiveData(1)
val subject = liveData(testScope.coroutineContext) {
emitSource(subLiveData)
emitSource(subLiveData) //crashes
}
subject.addObserver().apply {
testScope.advanceUntilIdle()
}
}

il...@google.com <il...@google.com> #6Jan 27, 2022 11:20PM

With 2.2.0-alpha04 (that use Main.immediate), the issue seems to be still there (I tested it by calling emitSource() twice, like your test case)

ih...@gmail.com <ih...@gmail.com> #7Jan 27, 2022 11:35PM

yea sorry immediate does not fix it.
I actually have a WIP fix for it:

https://android-review.googlesource.com/c/platform/frameworks/support/+/1112186

if your case is the one i found (emitting same LiveData multiple times, as shown in #5) you can work around it by adding a dummy transformation.

val subLiveData = MutableLiveData(1)
val subject = liveData(testScope.coroutineContext) {
emitSource(subLiveData.map {it })
emitSource(subLiveData.map {it} )
}

b9...@gmail.com <b9...@gmail.com> #8Jan 28, 2022 07:54AM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit af12e75e6b4110f48e44ca121466943909de8f06
Author: Yigit Boyar <yboyar@google.com>
Date: Tue Sep 03 12:58:11 2019

Fix coroutine livedata race condition

This CL fixes a bug in liveData builder where emitting same
LiveData source twice would make it crash because the second
emission registry could possibly happen before first one is
removed as source.

We fix it by using a suspending dispose function. It does feel
a bit hacky but we cannot make DisposableHandle.dispose async
and we do not want to block there. This does not mean that there
is a problem if developer disposes it manually since our emit
functions take care of making sure it disposes (and there is
no other way to add source to the underlying MediatorLiveData)

Bug: 140249349
Test: BuildLiveDataTest#raceTest_*

Change-Id: I0b464c242a583da4669af195cf2504e2adc4de40

M lifecycle/lifecycle-livedata-ktx/api/2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/current.txt
M lifecycle/lifecycle-livedata-ktx/api/public_plus_experimental_2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/public_plus_experimental_current.txt
M lifecycle/lifecycle-livedata-ktx/api/restricted_2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/restricted_current.txt
M lifecycle/lifecycle-livedata-ktx/src/main/java/androidx/lifecycle/CoroutineLiveData.kt
M lifecycle/lifecycle-livedata-ktx/src/test/java/androidx/lifecycle/BuildLiveDataTest.kt

https://android-review.googlesource.com/1112186

https://goto.google.com/android-sha1/af12e75e6b4110f48e44ca121466943909de8f06

ra...@google.com <ra...@google.com> Feb 1, 2022 11:11PM

Assigned to ra...@google.com.

ap...@google.com <ap...@google.com> #9Feb 2, 2022 10:14PM

Project: platform/frameworks/support
Branch: androidx-main

commit 97993ad954cb98211ef52b6e26c7877dbdeeec1c
Author: Jeremy Woods <jbwoods@google.com>
Date: Tue Feb 01 17:06:11 2022

Bump lifecycle process start-up dependency to 1.1.1

Bumping the startup dependency to include aosp/1855769.

RelNote: "Updated `lifecycle-process` to depend on [Startup 1.1.1](/jetpack/androidx/releases/startup#1.1.1) to ensure that fixes that prevent `ProcessLifecycleInitializer` from throwing a `StartupException` are available by default."
Bug: 216490724
Test: tested in sample app

Change-Id: Ib01dfbba1d63aa03e43e09ee8886cc76e1050e1b

M lifecycle/lifecycle-process/build.gradle

https://android-review.googlesource.com/1964554

jb...@google.com <jb...@google.com> #10Feb 2, 2022 10:22PM

Marked as fixed.

This has been fixed internally and will be released in the Lifecycle 2.5.0-alpha02 release.

b9...@gmail.com <b9...@gmail.com> #11Feb 6, 2022 06:12PM

When will start-up 1.1.1 release?

ra...@google.com <ra...@google.com> #12Feb 7, 2022 04:59PM

It should be out before the end of the week.