| commit | 5fe62adfa9d530f4615a64d6f123a380beb61d9c | [log] [tgz] |
|---|---|---|
| author | Jeremy Woods <[email protected]> | Wed Feb 21 22:47:46 2024 +0000 |
| committer | Jeremy Woods <[email protected]> | Thu Feb 22 19:17:36 2024 +0000 |
| tree | b97ad66cf82986c5a8ecb3614d20ef77ca6342ba | |
| parent | ef6c37a4fd6ac86083facefc793b3ef9465b2adf [diff] |
Fix issue with failing to cancel forward transitions Prior to the Predictive back world, it was not possible to cancel any transactions. They were atomic in nature and executing one meant that it would finish. In the new world that is no longer the case, specifically if you begin a forward transacation it is possible to start a predictive back in the middle of that. Currently, when you do this with Androidx Transitions, the view you are seeking away from is immediately destroyed and if you do not complete the back gesture, you are left with a blank screen. What we should do instead is to immediately complete the forward transaction, then begin the back gesture as if you had started from a resumed fragment. This gets us into a known state that we can correctly recover from. RelNote: "Fixed an issue in Fragments where interrupting incoming transitions with a Predictive back gesture would destroy the entering view, potentially leaving a blank screen." Test: Added FragmentTransitionSeekingTest Bug: 319531491 Change-Id: Id3f228dd5f53742c68e6cb16b752022e18e00ec9
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.