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

Please include a sample project that reproduces your issue.

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

Sample project attached. Just add to plain project this dependencies allow to reproduce.

def emoji2_version = "1.1.0-beta01"
implementation "androidx.emoji2:emoji2:$emoji2_version"

def lifecycle_version = "2.5.0-alpha01"
implementation "androidx.lifecycle:lifecycle-process:$lifecycle_version"

lifecycle-process-crash.zip

106 KB

Download

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

The reason may be related to this change, which check itself before it is initialized. Use 2.4.0 of lifecycle-process as workaround.

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

Yes, this is due to this change, as well as the fact that EmojiCompatInitializer has a ProcessLifecycleInitializer as a dependency and also re-calls it, but in manual mode.

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

ProcessLifecycleInitializer is expected to already be initialized (via the manifest provider for App Startup) by the time that code runs - App Startup shouldn't be calling create if that component has already been initialized, hence you shouldn't get any exception. We'll take a look on where things are breaking down though.

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

Thanks for the answer.

As I understand EmojiCompatInitializer has ProcessLifecycleInitializer as a dependency. That is mean, the ProcessLifecycleInitializer must be executed before the EmojiCompatInitializer, which in its create method calls the delayUntilFirstResume method, which in turn calls the ProcessLifecycleInitializer via appInitializer.initializeComponent(ProcessLifecycleInitializer.class)

Maybe it would be more correct to create a bug in emoji-2, but let it be here.

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

This issue isn't related to emoji2, it could be reproduced easily with the lifecycle-process (2.4.0 -> 2.5.0-alpha01) only.

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.