IssueTracker

Can you include a sample project that crashes in release mode?

For us this is only happening in places where LifecycleEventEffect is used. Example stacktrace:

Fatal Exception: java.lang.IllegalStateException
CompositionLocal LocalLifecycleOwner not present
androidx.lifecycle.compose.LocalLifecycleOwnerKt$LocalLifecycleOwner$1$1.invoke (LocalLifecycleOwner.android.kt:63)
androidx.lifecycle.compose.LocalLifecycleOwnerKt$LocalLifecycleOwner$1$1.invoke (LocalLifecycleOwner.android.kt:62)
kotlin.SynchronizedLazyImpl.getValue (LazyJVM.kt:74)
androidx.compose.runtime.LazyValueHolder.getCurrent (LazyValueHolder.java:29)
androidx.compose.runtime.LazyValueHolder.getValue (LazyValueHolder.java:31)
androidx.compose.runtime.CompositionLocalMapKt.read (CompositionLocalMap.kt:90)
androidx.compose.runtime.ComposerImpl.consume (Composer.kt:2135)
androidx.lifecycle.compose.LifecycleEffectKt.LifecycleEventEffect (LifecycleEffect.kt:748)
com.freeletics.feature.profile.ProfileUiKt$ProfileUi$1.invoke (ProfileUi.kt:62)

This is also on Lifecycle 2.8.2 with Compose 1.6.

Here is a sample project

https://github.com/nilsjr/Koncept

• Checkout repository
• Build release apk with ./gradlew :app:assembleRelease -PenableReleaseSigning=true
• App starts without crash
• Comment or remove line 14 in https://github.com/nilsjr/Koncept/blob/develop/app/proguard-rules.pro
• Build release apk with ./gradlew :app:assembleRelease -PenableReleaseSigning=true
• App crashing on start

FATAL EXCEPTION: main (Ask Gemini)
  Process: de.nilsdruyen.koncept, PID: 5880
  java.lang.IllegalStateException: CompositionLocal LocalLifecycleOwner not present
  ...

comment#4:

Thank you for sharing the sample project. I can confirm that I was able to reproduce the issue, and that your workaround works. I will investigate the problem further.

It appears that the custom ProGuard rule was not working as intended across all projects.

However, using public static *** getLocalLifecycleOwner(); (with the wildcard type ***) seems to work consistently in the sample project and our internal experiments:

-if public class androidx.compose.ui.platform.AndroidCompositionLocals_androidKt {
    public static *** getLocalLifecycleOwner();
}
-keep public class androidx.compose.ui.platform.AndroidCompositionLocals_androidKt {
    public static *** getLocalLifecycleOwner();
}

We are investigating further, and we will be working on a fix for the issue.

Could you please make an immediate patch release as 2.8.2 crashes with the above exception?

comment#8:

These changes are scheduled to be included in our upcoming hot-fix release, version 2.8.3.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.lifecycle:lifecycle-runtime-compose:2.8.3
• androidx.lifecycle:lifecycle-runtime-compose-android:2.8.3
• androidx.lifecycle:lifecycle-runtime-compose-desktop:2.8.3

It seems that Lifecycle 2.8.3 is not available on Google's Maven repository: https://maven.google.com/web/index.html#androidx.lifecycle:lifecycle-runtime-compose Any idea when it will be deployed?

comment#11:

There was a mix-up, and the Lifecycle 2.8.3 artifacts won't be available until Monday. Sorry for the false alarm.

Seems to be good now. Thanks!

Lifecycle 2.8.3 is now available on maven.google.com.

comment#15:

I'm unable to offer advice since I can't replicate the issue you're experiencing -- but based on your message, it appears Lifecycle "should" be working correctly.

Would you please create a separated issue and include a sample project that reproduces the problem you're encountering?

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.lifecycle:lifecycle-runtime-compose:2.9.0-alpha01
• androidx.lifecycle:lifecycle-runtime-compose-android:2.9.0-alpha01
• androidx.lifecycle:lifecycle-runtime-compose-desktop:2.9.0-alpha01

@ comment #17:

Lifecycle does not have a transitive dependency on Compose since it's not strictly related to Compose. It's more like Compose 1.7 has been adjusted to Lifecycle 2.8.0. So you need to explicitly update your Compose dependencies.

comment#17:

lifecycle-runtime-compose 2.8.* does not explicitly depend on compose-ui 1.7.* but there is a behavior compatibility issue between the versions - meaning standard POM dependency version checks will not detect the problem.

To understand the issue better, let’s go step by step on what happened:

• We have introduced a new LocalLifecycleOwner inside lifecycle-runtime-compose.
• We have inverted the dependency between compose-ui and lifecycle-runtime-compose.
  • Before: lifecycle-runtime-compose - depends on -> compose-ui.
  • After: compose-ui - depends on -> lifecycle-runtime-compose.
• We have changed the “old” LocalLifecycleOwner from compose-ui to return the new one in lifecycle-runtime-compose for binary compatibility.
  • compose-ui 1.6.*, sets up the “old” LocalLifecycleOwner at runtime.
  • compose-ui 1.7.*, sets up the “new” LocalLifecycleOwner at runtime.
• lifecycle-runtime-compose 2.7.* needs the “old” LocalLifecycleOwner.
• lifecycle-runtime-compose 2.8.* needs the “new” LocalLifecycleOwner.

Now, when combining compose-ui 1.6.* and lifecycle-runtime-compose 2.8.* or compose-ui 1.7.* and lifecycle-runtime-compose 2.7.*, they will reference to different LocalLifecycleOwner instances at runtime.

Since there's no direct dependency between them, standard POM checks cannot detect this issue. A call chain analysis would have been required to identify the behavior incompatibility between stable versions.

Looking at the changelogs from lifecycle 2.8.1 I assume this fix was not released?

Lifecycle 2.8.1 was released last week (May 29, 2024). The workaround was merged yesterday (June 4, 2024), so it is not included in version 2.8.1. Please note that the "Date: Wed May 29" in the CL header above is a metadata that indicates when the CL was created, not when it was merged.

We intend to include it in the very next release, Lifecycle 2.8.2.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.lifecycle:lifecycle-runtime-compose:2.8.2
• androidx.lifecycle:lifecycle-runtime-compose-android:2.8.2
• androidx.lifecycle:lifecycle-runtime-compose-desktop:2.8.2

Can confirm, the issue reproduces on release build

Same for me too. I updated the Lifecycle lib to v2.8.2 and Compose BOM to v2024.06.00 which incorporate v1.6.8 of Compose libs. Still, the app got this exception and crashed, but only in the release mode and not in debug mode. Unfortunately, I got the crash in the production app after its release. After downgrading the Lifecycle lib to v2.7.0, it is working fine in the production app. Immediately, I had to release another patch version, so the users do not complain about app not working.

Comment #26, Comment #27, Comment #28, Comment #29, Comment #30:

We have received a similar report at b/346808608, where the author suggests a workaround (adding -keep class androidx.compose.ui.platform.AndroidCompositionLocals_androidKt { *; } to your ProGuard rules).

Although we have included a custom ProGuard rule as part of our fix, the rule is not working as intendend across all projects. We are currently investigating the problem, see here for more details.

I can confirm it's still an issue for me with Compose BOM "2024.06.00" and lifecycle 2.8.2.

I added these lines to proguard to fix the issue:

-if public class androidx.compose.ui.platform.AndroidCompositionLocals_androidKt {
    public static *** getLocalLifecycleOwner();
}
-keep public class androidx.compose.ui.platform.AndroidCompositionLocals_androidKt {
    public static *** getLocalLifecycleOwner();
}

Following up on the issue mentioned in comment#26: a fix for b/346808608 is scheduled to be included in our upcoming hot-fix release, version 2.8.3 -- for additional details, please refer to this comment.

Following up on the issue mentioned in comment#26: there was a mix-up, and the Lifecycle 2.8.3 artifacts won't be available until Monday.

Lifecycle 2.8.3 is now available on maven.google.com.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.lifecycle:lifecycle-runtime-compose:2.9.0-alpha01
• androidx.lifecycle:lifecycle-runtime-compose-android:2.9.0-alpha01
• androidx.lifecycle:lifecycle-runtime-compose-desktop:2.9.0-alpha01