In LifecycleStartEffect, onStopOrDispose gets called twice [352364595]

Fixed

Bug

Status Update

No update yet.

Description

no...@gmail.com

created issue #1

Jul 11, 2024 04:25PM

Component used: androidx.lifecycle:lifecycle-runtime-compose

Version used: 2.7.0

Devices/Android versions reproduced on: API 34 emulator

To reproduce:

Navigate to an Android Fragment with the following:

LifecycleStartEffect {
    println("Setup")
    onStopOrDispose {
        println("Cleanup")
    }
}

Observe "Setup" is printed once.
Hit back to close the Fragment.
Observe "Cleanup" is printed twice.

Comments

il...@google.com <il...@google.com> Jul 11, 2024 11:06PM

Assigned to mg...@google.com.

mg...@google.com <mg...@google.com> Jul 12, 2024 01:57PM

Accepted by mg...@google.com.

ap...@google.com <ap...@google.com> #2Jul 15, 2024 08:41PM

Marked as fixed.

To use Lifecycle 2.8.0-alpha03, ensure you are using at least Compose UI 1.7.0-alpha05.

The issue is happening because, starting from Lifecycle 2.8.0-alpha03 and Compose UI 1.7.0-alpha05, LocalLifecycleOwner has been moved from androidx.compose.ui to lifecycle-runtime-compose, as outlined in their respective release notes. For compatibility reasons, you must update both dependencies.

For context, note these changes were made to enable the utilization of its Compose-based helper APIs beyond Compose UI (such as in Molecule). Further information can be found at b/328263448.

If the issue persists even after updating your Compose UI, please let us know.

Edit: please see https://issuetracker.google.com/336842920#comment8 for a workaround.

pr...@google.com <pr...@google.com> #3Aug 13, 2024 06:58PM

Thanks for your answer.
If this change has made both libraries version dependent, it seems that guide them to the release note so that users will not experience difficulties :)

Issue 352364595

Description

Issue summary

Comments

il...@google.com <il...@google.com> Jul 11, 2024 11:06PM

mg...@google.com <mg...@google.com> Jul 12, 2024 01:57PM

ap...@google.com <ap...@google.com> #2Jul 15, 2024 08:41PM

pr...@google.com <pr...@google.com> #3Aug 13, 2024 06:58PM

Add comment

Issue metadata