commit | 448093dd529e151c486343aedcfb1f656abe9819 | [log] [tgz] |
---|---|---|
author | Jeremy Woods <jbwoods@google.com> | Tue Sep 13 13:34:06 2022 -0700 |
committer | Jeremy Woods <jbwoods@google.com> | Wed Sep 14 07:26:06 2022 -0700 |
tree | d5555454fcf0463ccd6f2d164a43d0f5a7df340c | |
parent | 5e9ff19e471b5c0e82c1971977fe9447ad2f2d8c [diff] |
Dispatch config change on added fragmentManagers With the new provider callbacks, each fragment manager registers for config change with the host once it is attached, and does not unregister until it is destroyed. This means that even after fragments have been put on the back stack, their childFragmentManagers can still dispatch config changes, even though the fragment is not currently added. We need to make it so that only added fragments (and their child fragment managers) dispatch config changes. RelNote: "Fixed an error that caused fragments on the back stack to get onConfigurationChanged() callbacks." Test: Added ProviderCallbackTest Bug: 242570955 Fixes: 243982866 Change-Id: I8dfe68f7b8700f0c1d3b13a3d5b826fc924b7452
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.