IssueTracker

Same problem here. Lifecycle 2.8.0 is now stable but Compose UI 1.7.0 is still beta. Of course our Dependabot didn't know about this relationship between dependencies 😬

Something like that really shouldn't happen... 🤦🏻‍♂️

Thats really really bad. I would always expect the latest stable versions to be compatible. Please add this requirement to the changelog or better add a warning at compile time if used with incompatible combinations.

We acknowledge that the behavior dependency between Lifecycle 2.8 Stable and Compose 1.7 Beta is not ideal. This should not have occurred, and we are working in a fix and looking into how we can prevent it in the future. We have updated our release notes to clarify this issue.

In the meantime, while Compose 1.7 Stable has not been released, we have outlined some potential workarounds below. Please note that these solutions are not perfect but they could be helpful to some of you while the fix is not ready:

1. Use Compose 1.7 Beta if that is an option for you.

2. Map androidx.compose.ui.platform.LocalLifecycleOwner (Compose 1.6) to androidx.lifecycle.compose.LocalLifecycleOwner (Lifecycle 2.8). Here's an example:

   CompositionLocalProvider(
       androidx.lifecycle.compose.LocalLifecycleOwner provides androidx.compose.ui.platform.LocalLifecycleOwner.current,
   ) {
     // ...
   }
   

   • Please note that when using Navigation Compose, this may be required on each navigation page (for more details, refer to comment #11).

3. Manually pass androidx.compose.ui.platform.LocalLifecycleOwner (Compose 1.6) to Lifecycle 2.8 methods. For instance:

   val state by stateFlow.collectAsStateWithLifecycle(
     owner = androidx.compose.ui.platform.LocalLifecycleOwner.current
   )
   

Thank you.

Thanks for the workaround!

the option 2) will not work with compose navigation component, right ? As the lib also provides a LocalLifecycleOwner and 3) will not work for any library that uses LocalLifecycleOwner internally.

comment#10:

the option 2) will not work with compose navigation component, right ? As the lib also provides a LocalLifecycleOwner

Yes, you would need to also include it on each navigation page (composable() route).

3. will not work for any library that uses LocalLifecycleOwner internally.

Yes.

For the record, the new dropUnlessResumed and dropUnlessStarted APIs won't work with Navigation 2.7 out of the box. Similar to the fix above, the new LocalLifecycleOwner needs to be explicitly assigned to the NavBackStackEntry in every composable() route.

composable(...) { navBackStackEntry ->
  CompositionLocalProvider(
    androidx.lifecycle.compose.LocalLifecycleOwner provides navBackStackEntry
  ) {
    MyScreen(
      onBackClick = dropUnlessResumed { navController.popBackStack() }
    )
  }
}

Comment #14 seems to work when collecting a stateflow from a viewmodel :)

The release notes of Lifecycle stated that "lifecycle-*:2.8.0 requires a minimum Compose version of 1.7.0-alpha05". However when I run ./gradlew app:dependencies --configuration releaseRuntimeClasspath I couldn't find any Compose library resolved to alpha versions, the highest version was 1.6.5.

Is the statement correct? Or do I misinterpret it?

@ 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