lifecycle-runtime-compose:2.8.0-alpha03 occurs CompositionLocal LocalLifecycleOwner not present Error [336842920]

Fixed

Bug

Status Update

No update yet.

Description

gr...@gmail.com

created issue #1

Apr 25, 2024 01:26AM

Component used:

Version used:
lifecycle-runtime-compose:2.8.0-alpha03
androidx.compose.ui:ui-android:1.7.0-alpha03

When

Devices/Android versions reproduced on: Android14

When running collectAsStateWithLifecycle in setContent inside the fragment, the following error occurs.
Could any of the changes in lifecycle 2.8.0-alpha03 be caused by LocalLifecycleOwner's has different directory?

"LocalLifecycleOwner moved from Compose UI to lifecycle-runtime-compose so that its Compose-based helper APIs can be used outside of Compose UI"

https://developer.android.com/jetpack/androidx/releases/lifecycle#2.8.0-alpha03

java.lang.IllegalStateException: CompositionLocal LocalLifecycleOwner not present
at androidx.lifecycle.compose.LocalLifecycleOwnerKt$LocalLifecycleOwner$1.invoke(LocalLifecycleOwner.kt:26)
at androidx.lifecycle.compose.LocalLifecycleOwnerKt$LocalLifecycleOwner$1.invoke(LocalLifecycleOwner.kt:25)
at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
at androidx.compose.runtime.LazyValueHolder.getCurrent(ValueHolders.kt:29)
at androidx.compose.runtime.LazyValueHolder.getValue(ValueHolders.kt:31)
at androidx.compose.runtime.CompositionLocalMapKt.read(CompositionLocalMap.kt:90)
at androidx.compose.runtime.ComposerImpl.consume(Composer.kt:2135)
at androidx.lifecycle.compose.FlowExtKt.collectAsStateWithLifecycle(FlowExt.kt:180)

Thu Apr 25 2024 10:23:11 GMT+0900 (한국 표준시).png

134 KB

View

Download

Comments

mg...@google.com <mg...@google.com> #2Apr 25, 2024 01:52PM

Status: Won't Fix (Intended Behavior)

Project: platform/frameworks/support
Branch: androidx-master-dev

commit d0a10be065a3a629e3835f28d35804c91d8d2e4d
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1427352

Message last modified on May 16, 2024 09:44AM

gr...@gmail.com <gr...@gmail.com> #3Apr 25, 2024 02:02PM

We've updated the error message to make it more clear what destination you're currently on - this will help you determine if your call to setGraph() hasn't happened yet (you have a null current destination) or if you've popped to another destination unexpectedly.

ma...@marcardar.com <ma...@marcardar.com> #4May 15, 2024 06:05AM

Project: platform/frameworks/support
Branch: snap-temp-L69500000699825513

commit 6ada6bd039f4a28d2760f4912093abc60ab54d84
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436733

sj...@gmail.com <sj...@gmail.com> #5May 15, 2024 08:33AM

Project: platform/frameworks/support
Branch: snap-temp-L62000000699827533

commit e5780347bfba28e4a500bd964d273c282c12dceb
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436737

ha...@gmail.com <ha...@gmail.com> #6May 15, 2024 11:12AM

Project: platform/frameworks/support
Branch: snap-temp-L46100000699831674

commit 7ab7f8b1967945ba0d506120dbc070ecbfb37c13
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436741

th...@gmail.com <th...@gmail.com> #7May 15, 2024 12:40PM

Project: platform/frameworks/support
Branch: snap-temp-L91000000699844097

commit 4101ca222554fdfae678ff1e6e47b1a4ab319a56
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436542

Message last modified on May 15, 2024 12:40PM

mg...@google.com <mg...@google.com> #8May 15, 2024 03:04PM

Project: platform/frameworks/support
Branch: snap-temp-L34200000699848945

commit 0da3ed71fa5545646d44fb44219b31e7e5621f8f
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436745

Message last modified on Jun 11, 2024 03:06PM

mg...@google.com <mg...@google.com> May 15, 2024 04:13PM

Status: Won't Fix (Intended Behavior)

th...@tempo.co.nz <th...@tempo.co.nz> #9May 15, 2024 11:40PM

Project: platform/frameworks/support
Branch: snap-temp-L04700000699849955

commit 12b13608ec1155b5780fe44f5ab07cdc93c5ba90
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436750

ju...@veepee.com <ju...@veepee.com> #10May 16, 2024 03:25PM

Project: platform/frameworks/support
Branch: snap-temp-L69500000699869549

commit 7204d04ad74baf9816389e27778266391fbd79a5
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436913

mg...@google.com <mg...@google.com> #11May 16, 2024 06:21PM

Project: platform/frameworks/support
Branch: snap-temp-L31300000699869852

commit 398a1fe7bb7792589189574aec5f6e77bb749229
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436917

Message last modified on May 17, 2024 02:58PM

sj...@gmail.com <sj...@gmail.com> #12May 17, 2024 12:38PM

Project: platform/frameworks/support
Branch: snap-temp-L53700000699921463

commit 31027c16ff20b10e78093f8de205c81fc49dfc92
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436920

ap...@google.com <ap...@google.com> #13May 21, 2024 07:00PM

Project: platform/frameworks/support
Branch: snap-temp-L25200000699921867

commit 63e58ff4f522eb70dec6c0749679fb6b963698d8
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436924

bo...@gmail.com <bo...@gmail.com> #14May 21, 2024 11:34PM

Project: platform/frameworks/support
Branch: snap-temp-L07700000699933785

commit 56fe0d47de20fb430c4280332a20eb96076dd44b
Author: Ian Lake <ilake@google.com>
Date: Mon Sep 14 16:10:06 2020

Mention the current destination in getBackStackEntry errors

Improve the debugging experience for "No destination
with ID..." errors in getBackStackEntry() by mentioning
exactly destination the NavController is on. This would
allow developers to know if they have called popBackStack()
to a destination they don't expect to be at or if
they have not called setGraph() at all (where the
current destination would be null).

Test: existing tests pass
BUG: 168311416
Change-Id: Ia96b6732d7caadbddf31b7f35a1a419407ff6e25
(cherry picked from commit d0a10be065a3a629e3835f28d35804c91d8d2e4d)

M navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/1436929

ra...@gmail.com <ra...@gmail.com> #15May 22, 2024 06:43PM

Comment has been deleted.

Message last modified on May 22, 2024 06:50PM

ma...@gmail.com <ma...@gmail.com> #16May 26, 2024 08:11PM

Could we further improve this by indicating the name of the destination instead of just the ID number?

fi...@gmail.com <fi...@gmail.com> #17May 30, 2024 08:41AM

If you use a resource to provide the name it will already be displayed. Along with any route or label you may have added.

sj...@gmail.com <sj...@gmail.com> #18May 30, 2024 08:46AM

We are also getting this error even after ensuring we are setting the graph before using .popBackStack().

Is there any way to safeguard against this? I am not able to reproduce the error myself, but get a lot of errors show up in Crashlytics

mg...@google.com <mg...@google.com> #19May 30, 2024 01:25PM

I have the same problem

Message last modified on Jun 5, 2024 01:39PM

fi...@wartek.belajar.id <fi...@wartek.belajar.id> #20May 31, 2024 03:24AM

Comment has been deleted.

Message last modified on May 31, 2024 03:24AM

mg...@google.com <mg...@google.com> Jun 4, 2024 10:18PM

Status: In Progress (Accepted) (reopened)

ap...@google.com <ap...@google.com> #21Jun 4, 2024 10:24PM

Marked as fixed.

Same problem here

ca...@careem.com <ca...@careem.com> #22Jun 5, 2024 08:32AM

Same problem here

mg...@google.com <mg...@google.com> #23Jun 5, 2024 09:45AM

Same problem here

Message last modified on Jun 5, 2024 10:19AM

va...@cloudkitchens.com <va...@cloudkitchens.com> #24Jun 7, 2024 12:52PM

Same problem here, currently using version 2.7.7

pr...@google.com <pr...@google.com> #25Jun 12, 2024 10:45PM

same problem here

li...@gmail.com <li...@gmail.com> #26Jun 14, 2024 02:02AM

I have updated to 2.8.2, and everything works when building debug. However, if I build the release with ProGuard, it still crashes with the error "CompositionLocal LocalLifecycleOwner not present".

eg...@gmail.com <eg...@gmail.com> #27Jun 14, 2024 06:15AM

Can confirm, the issue reproduces on release build

[Deleted User] <[Deleted User]> #28Jun 14, 2024 07:59AM

the same, in 2.8.2 it's still crashing on release builds, debug builds are ok

Message last modified on Jun 14, 2024 08:00AM

ma...@gmail.com <ma...@gmail.com> #29Jun 14, 2024 09:28AM

Same for me, version 2.8.2. debug builds is ok, release crashes

Message last modified on Jun 14, 2024 09:29AM

kr...@gmail.com <kr...@gmail.com> #30Jun 14, 2024 09:52AM

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.

mg...@google.com <mg...@google.com> #31Jun 14, 2024 10:28AM

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.

Message last modified on Jun 21, 2024 10:17AM

ba...@gmail.com <ba...@gmail.com> #32Jun 19, 2024 07:44AM

Same problem for me.
Updating to 2.8.2 with Compose BOM "2024.06.00" the app is crashing on Release build with the error "CompositionLocal LocalLifecycleOwner not present".
A proguard rules should be provided or another version with fix.

su...@gmail.com <su...@gmail.com> #33Jun 25, 2024 06:32PM

I can confirm, that the issue persists on the 2.8.2 version in the release build.

However, for the visitors

"-keep class androidx.compose.ui.platform.AndroidCompositionLocals_androidKt { *; }"

Add this to your app proguard file and it'll work fine.

Message last modified on Jun 25, 2024 06:32PM

ih...@enverus.com <ih...@enverus.com> #34Jun 26, 2024 12:30PM

Comment has been deleted.

Message last modified on Jun 26, 2024 12:31PM

mo...@gmail.com <mo...@gmail.com> #35Jun 26, 2024 12:32PM

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();
}

mg...@google.com <mg...@google.com> #36Jun 27, 2024 03:54PM

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.

Message last modified on Jun 27, 2024 03:55PM

mg...@google.com <mg...@google.com> #37Jun 29, 2024 09:57AM

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.

mg...@google.com <mg...@google.com> #38Jul 2, 2024 08:32AM

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

Message last modified on Jul 2, 2024 08:32AM

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

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

Issue 336842920

Description

Issue summary

Comments

mg...@google.com <mg...@google.com> #2Apr 25, 2024 01:52PM

gr...@gmail.com <gr...@gmail.com> #3Apr 25, 2024 02:02PM

ma...@marcardar.com <ma...@marcardar.com> #4May 15, 2024 06:05AM

sj...@gmail.com <sj...@gmail.com> #5May 15, 2024 08:33AM

ha...@gmail.com <ha...@gmail.com> #6May 15, 2024 11:12AM

th...@gmail.com <th...@gmail.com> #7May 15, 2024 12:40PM

mg...@google.com <mg...@google.com> #8May 15, 2024 03:04PM

mg...@google.com <mg...@google.com> May 15, 2024 04:13PM

th...@tempo.co.nz <th...@tempo.co.nz> #9May 15, 2024 11:40PM

ju...@veepee.com <ju...@veepee.com> #10May 16, 2024 03:25PM

mg...@google.com <mg...@google.com> #11May 16, 2024 06:21PM

sj...@gmail.com <sj...@gmail.com> #12May 17, 2024 12:38PM

ap...@google.com <ap...@google.com> #13May 21, 2024 07:00PM

bo...@gmail.com <bo...@gmail.com> #14May 21, 2024 11:34PM

ra...@gmail.com <ra...@gmail.com> #15May 22, 2024 06:43PM

ma...@gmail.com <ma...@gmail.com> #16May 26, 2024 08:11PM

fi...@gmail.com <fi...@gmail.com> #17May 30, 2024 08:41AM

sj...@gmail.com <sj...@gmail.com> #18May 30, 2024 08:46AM

mg...@google.com <mg...@google.com> #19May 30, 2024 01:25PM

fi...@wartek.belajar.id <fi...@wartek.belajar.id> #20May 31, 2024 03:24AM

mg...@google.com <mg...@google.com> Jun 4, 2024 10:18PM

ap...@google.com <ap...@google.com> #21Jun 4, 2024 10:24PM

ca...@careem.com <ca...@careem.com> #22Jun 5, 2024 08:32AM

mg...@google.com <mg...@google.com> #23Jun 5, 2024 09:45AM

va...@cloudkitchens.com <va...@cloudkitchens.com> #24Jun 7, 2024 12:52PM

pr...@google.com <pr...@google.com> #25Jun 12, 2024 10:45PM

li...@gmail.com <li...@gmail.com> #26Jun 14, 2024 02:02AM

eg...@gmail.com <eg...@gmail.com> #27Jun 14, 2024 06:15AM

[Deleted User] <[Deleted User]> #28Jun 14, 2024 07:59AM

ma...@gmail.com <ma...@gmail.com> #29Jun 14, 2024 09:28AM

kr...@gmail.com <kr...@gmail.com> #30Jun 14, 2024 09:52AM

mg...@google.com <mg...@google.com> #31Jun 14, 2024 10:28AM

ba...@gmail.com <ba...@gmail.com> #32Jun 19, 2024 07:44AM

su...@gmail.com <su...@gmail.com> #33Jun 25, 2024 06:32PM

ih...@enverus.com <ih...@enverus.com> #34Jun 26, 2024 12:30PM

mo...@gmail.com <mo...@gmail.com> #35Jun 26, 2024 12:32PM

mg...@google.com <mg...@google.com> #36Jun 27, 2024 03:54PM

mg...@google.com <mg...@google.com> #37Jun 29, 2024 09:57AM

mg...@google.com <mg...@google.com> #38Jul 2, 2024 08:32AM

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

Add comment

Issue metadata