commit | 59dd212495f4378911cbb310367743b2aae734a3 | [log] [tgz] |
---|---|---|
author | Marcello Galhardo <mgalhardo@google.com> | Wed May 29 17:49:02 2024 +0100 |
committer | Marcello Galhardo <mgalhardo@google.com> | Fri May 31 22:41:35 2024 +0100 |
tree | 5cbd039b75034adbafc25de5b0be554de92f144f | |
parent | a25ffd4b1babae03d63f8c1ab13dc4c638291df9 [diff] |
Make `LocalLifecycleOwner` backward compatible with Compose 1.6.* Lifecycle 2.8.* requires Compose 1.7.* for correctness, but Compose 1.7.* have not yet reached stable. For allowing Lifecycle 2.8.* to be used with Compose 1.6.*, we are introducing the following measures: * When Lifecycle 2.8.* detects it's running with Compose 1.6.*, it uses reflection to access the previous version of `androidx.compose.ui.platform.LocalLifecycleOwner`. * A custom Proguard rule has been added to prevent the obfuscation of `androidx.compose.ui.platform.LocalLifecycleOwner` when using Compose 1.6.*. This ensures the reflection approach works correctly. We have tested these backward compatibility measures in various scenarios, including: * Projects with and without Navigation Compose integrated. * Compose versions 1.6.* and 1.7.*. * Builds both with and without Proguard obfuscation applied. Please note that backward compatibility reflection will be removed once Compose 1.7.* is stable. A Gradle dependency constraint should be put in place to ensure smooth migration for clients. Fixes: b/336842920 Test: manual Change-Id: I3d0666a88eb309aae9a5c60eacc6818f52dd0bfd
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.