|author||Chuck Jazdzewski <firstname.lastname@example.org>||Wed Jun 22 14:17:20 2022 -0700|
|committer||Android Build Coastguard Worker <email@example.com>||Thu Jun 23 22:32:51 2022 +0000|
Remove tracking information from release recompose scopes Recompose scopes can be tracked by the recomposer past when they are removed from composition. Since it is expensive to accurately track the lifetime of scopes they are cleaned up lazily. This lazy cleanup might not trigger in some cases causing the references tracked by the scope to leak. This change first removes tracked references from recmpose scopes that are removed from composition and, second, reduces the chance that such scopes are tracked longer then necessary by cleaning up the conditionally invalid scopes table when scopes are removed. Fixes: 230168389 Test: ./gradlew :compose:r:r:tDUT Change-Id: Idfe3e3d5d6d65bac2cf06ee19fd00a5d9253d8a1 (cherry picked from commit 11dbe1f459907ec1c23e730c77e33de39fc894cf) Merged-In: Idfe3e3d5d6d65bac2cf06ee19fd00a5d9253d8a1
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/external directories in your checkout. All the dependencies in these directories are also available from
mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.