commit | 690f94c30462a839c39ef5298ec263b67a33557e | [log] [tgz] |
---|---|---|
author | Clara Fok <clarafok@google.com> | Tue Oct 10 13:38:34 2023 -0700 |
committer | Clara Fok <clarafok@google.com> | Tue Oct 10 14:27:46 2023 -0700 |
tree | 7b5b01725ea5740fdaa868db30b49cbd35d91713 | |
parent | 9db8b7b72176b164e552dff9611b4c58e7d8aeb1 [diff] |
Fix ViewModel not cleared after pop When an entry is popped followed by a configuration change, the list of transitioning entries is lost and the outgoing entry is not marked complete. As a result, the ViewModel is also not cleared. Now we ensure to mark outgoing entries as complete when a NavHost goes through config change (when it is disposed). Test: ./gradlew navigation:navigation-compose:cC Bug: 298164648 Relnote: "When an entry is popped followed by a configuration change, the entry's ViewModel will now be cleared properly if saveState is false." Change-Id: Idf242239ceeb731c3375ef507a2cc854d85743c7
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.