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

Will be this fix also part of 4.2 please?

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

for the "out" bundle issue, this seems indeed an issue. for the second one reported adding "debugUpdateAPKArtifact" to the path, this WAI as there can more more than one transformer and we need to automatically separate them so they do not use the same output folder. for #3, I will look at it but it might be difficult to change it at this time.

lifecycle-process-crash.zip

106 KB

Download

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

I understand that if there is more transformer is necessary to make every folder different, but there is the main problem, that the final one (last transform) is inside of the intermediate folder. The last transformation should end in the standard location, right? Maybe also with the default name not?

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

Hello, this is a P1 S1 issue for a while now, and it's blocking us from upgrading to AGP 4.2 and further. What's the current status? And do you have plans to backport it to 4.2.x?

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

no we don't have a plan to backport this. why is this blocking you from upgrading ?

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

We sign apk's and bundles via internal service, and i don't know another way to interact with artifacts; Yesterday i ended up with some ugly workaround: https://github.com/avito-tech/avito-android/pull/1085/files#diff-b898cc20fedebe394439bb37ffb91d3366a1f9a6d359dbdebca79af8a079f911 I'd be glad if you'll point me out how can it be done better.

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

I commented on the merge request but to summarize :

you can set your signing tasks output folder to wherever you need to be :

artifacts.use(target.tasks.signedApkTaskProvider(this)).configure { signedDirProperty.set(File("/path/to/where/you/want/your/signed/files")) }

if you don't set it, then we will set a directory automatically.

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

Thanks, Jerome!

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

Marked as fixed.

I checked that we do have correct behavior for FILE based artifacts like bundle :

> Task :app:debugUpdateArtifact
originalArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/intermediates/bundle/debug/signDebugBundle/app-debug.aab
updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/bundle/debug/app-debug.aab

however, we still seem to not be consistent for the DIRECTORY based artifacts like APK:

> Task :app:debugUpdateAPKArtifact
Input folder: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/apk/debug
Output folder: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/intermediates/apk/debug
Input file: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/apk/debug/app-debug.apk

Alex, can you have a look ?

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

correction, I was not correct about FILE being correct.

Instead of :

updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/bundle/debug/app-debug.aab

it should be

updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/app-debug.aab
``

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

Two requests are created as they are API changes b/241581686 (set artifact name for transformation) and b/241582907 (change string to OutputFile)