Status Update
No update yet.
Comments
ga...@freeletics.com
mg...@google.com
Ni...@fressnapf.com
> Jetifier is changing the import in the library to "androidx.core.os.ResultReceiver"
Config issue.
mg...@google.com
Branch: androidx-master-dev
commit 2bf39653103b1ce6b3b6fc64b44faaa9fcad1c19
Author: Filip Pavlis <pavlis@google.com>
Date: Tue Feb 12 19:41:53 2019
Revert changes in default.config and remove task.
It turned out that we have released (as part of beta03) mappings that
were not supposed to be used externally. This is because we were actively
maintaining "dejetifyArchive" task without realizing that next jetifier
update will contain such changes. As we are done with 28.0.0 I think it
is a good time to sunset the "dejetifyArchive" target. I also reverted
all the config changes that are not supposed to go outside. Please note
that there is still "partiallyDejetifyArchive" for migration purpouses
and is still part of continuous build.
Also added ignore rule for ResultReceiver.
Bug:
Bug:
Test: N/A
Change-Id: I59983d25ae7e0939f2e9e54005460ad0f73beb3c
M buildSrc/jetify.gradle
M buildSrc/src/main/kotlin/androidx/build/AndroidXPlugin.kt
M buildSrc/src/main/kotlin/androidx/build/LibraryVersions.kt
M jetifier/jetifier/core/src/main/resources/default.config
M jetifier/jetifier/core/src/main/resources/default.generated.config
mg...@google.com
nu...@traderepublic.com
Could you please make an immediate patch release as 2.8.2 crashes with the above exception?
pr...@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.8.3androidx.lifecycle:lifecycle-runtime-compose-android:2.8.3androidx.lifecycle:lifecycle-runtime-compose-desktop:2.8.3
m....@gmail.com
mg...@google.com
There was a mix-up, and the Lifecycle 2.8.3 artifacts won't be available until Monday. Sorry for the false alarm.
m....@gmail.com
Seems to be good now. Thanks!
mg...@google.com
Lifecycle 2.8.3 is now available on
pe...@mohemian.com
I'm still getting "java.lang.IllegalStateException: CompositionLocal LocalLifecycleOwner not present" with 2.8.3 in release builds (with obfuscation enabled). Adding
-keep class androidx.compose.ui.platform.AndroidCompositionLocals_androidKt { *; }
to my ProGuard rules fixes the issue. Any advice?
In my setup I have an app that's using the lifecycle dependencies directly, but some other dependencies of mine also include the same (and these libraries are obfuscated too) - not sure if this makes a difference.
mg...@google.com
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
pr...@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-alpha01androidx.lifecycle:lifecycle-runtime-compose-android:2.9.0-alpha01androidx.lifecycle:lifecycle-runtime-compose-desktop:2.9.0-alpha01
Description
This is basically an follow-up of
Component used:
Version used:
Devices/Android versions reproduced on: Android 14
We see the the following crashes directly at app start when using R8 (with default AGP 8.x fullMode enabled): IllegalStateException: CompositionLocal LocalLifecycleOwner not present
We saw the added proguard rules inhttps://android-review.googlesource.com/c/platform/frameworks/support/+/3105647/21/lifecycle/lifecycle-runtime-compose/proguard-rules.pro
Changing them to
fixes the crash.
So it seems the keep rule is currently not sufficient to make 2.8.2 compatible with Compose 1.6 when minify the build.