commit | eda11fe72e769430a2b673de132a5e9fed36a0c5 | [log] [tgz] |
---|---|---|
author | Jeremy Woods <jbwoods@google.com> | Fri Oct 13 21:28:40 2023 +0000 |
committer | Jeremy Woods <jbwoods@google.com> | Fri Oct 13 21:28:40 2023 +0000 |
tree | 7b00f67063d00f91ff59d4b5692a873524126224 | |
parent | 05bf95b7efbb8f9ea2a32060c23ef2efeed20a19 [diff] |
Ensure solo shared element transitions do not cause crashes There is a case where if you do either an add transaction with only a shared element transition or a replace transaction with only a shared element transition and manipulate the visiliblity of your fragment views, there is a NPE crash caused by having a null transition. While it is not correct to have a shared element transition without either an enter or exit transition with it, we should avoid crashing in that case. RelNote: "Fixed a `NullPointerException` caused by setting a shared element transition and failing to set an enter/exitTransition as well." Test: added FragmentTransitionTest Bug: 304304379 Bug: 301332995 Change-Id: I8472b865cf93d1d3463f73942c460263f746fef5
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.