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

We're working with the material team to ensure that Navigation matches the new material design guidelines.

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

Hi everyone. What is the progress or official decision on this one?

lifecycle-process-crash.zip

106 KB

Download

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

Hey guys, is there any progress on this issue? Can we expect these features to be implemented in the near future?"

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

Any update on this?

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

We'll update the bug here when there's updates to post. Suffice it to say, there's still work to do and we're dedicated to getting it done."

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

Hey guys, any update on this?"

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

The two biggest issues and annoyances of this bug for our end users with the new Navigation library and Bottom navigation bar are:
- Changing tab with the bottom bar resets the state and backstack of the previous tab/fragment, so our users are completely losing their navigation history (this is correctly implemented in Google Photos app)
- Pressing back from the root of one tab shows the initial tab/fragment instead of leaving the app"

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

I'm also facing this issue. Looking forward to the update.

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

Marked as fixed.

This solution saved my day

https://stackoverflow.com/a/51684125/5246711

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

Facing the same issue here. Any updates?

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

I'm also facing this issue, are there any updates?"