commit | 917c4a587b7071a9c99e8dcda43fb0c208ec19d5 | [log] [tgz] |
---|---|---|
author | Ian Lake <[email protected]> | Mon Oct 21 20:45:54 2024 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Wed Oct 23 01:18:49 2024 +0000 |
tree | 58446723cb46889243d9fbd5db10c9f0d43c28fe | |
parent | bec0ea6977ec04467c7b3fa6598cb0fa3d2db650 [diff] |
Prevent double expansion of transaction operations How predictive back with fragments works is that we pop the FragmentTransaction from the FragmentManager, but keep a copy of that transaction around in case the back operation is cancelled (either via gesture or interruption by changes to the FragmentManager). In the cancellation case, we then re-apply the same FragmentTransaction again, putting the FragmentManager back into the state it was in before the predictive back happened. However, when using operations that are 'expanded' like setPrimaryNavigationFragment(), we need to explicitly call collapseOps() before re-executing the operation so that we ensure that these transactions never have a direct reference to fragments from other transactions. By ensuring we only don't double expandOps(), we can avoid cases where FragmentManager does not allow references to previous fragments such as when using saveBackStack(). Relnote: "Fixed an `IllegalStateException` triggered by `saveBackStack` only after a Predictive Back gesture was cancelled or interrupted." Test: new PredictiveBackTest test cases BUG: 342419080 (cherry picked from https://android-review.googlesource.com/q/commit:922bb8acc3661be78480dd40f3c582af8b87f935) Merged-In: I3387d9d02495112f211448d7f3c9f862299da697 Change-Id: I3387d9d02495112f211448d7f3c9f862299da697
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.