commit | 5788ccb9d258ff40915749243249671636d51d8c | [log] [tgz] |
---|---|---|
author | Jeremy Woods <jbwoods@google.com> | Wed Sep 14 07:37:36 2022 -0700 |
committer | Jeremy Woods <jbwoods@google.com> | Wed Sep 14 07:42:29 2022 -0700 |
tree | ad58143e89306807caccec94a9bb16cc6ebd5c62 | |
parent | 448093dd529e151c486343aedcfb1f656abe9819 [diff] |
Dispatch Consumers only on added fragmentManagers The new providered callbacks are registered when the fragment manager is attached to the host, but not unregistered until destroyed. This means that fragments on the back stack can still have the callbacks dispatched to their child fragment managers, even though they are not added. aosp/2216147 already fixed this for config changes, but we need to fix it for multi-window, picture-in-picture, and on low memory modes. RelNote: "Fixed an error that caused fragments on the back stack to get onMultiWindowModeChanged(), onPictureInPictureModeChanged(), and onLowMemory() callbacks." Test: Added ProviderCallbackTests Change-Id: I34581e67bb3a81c7a7e162c3e47e51359896a628
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()
, jcenter()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.