commit | 928fdc3d271dd4799ba085245c4d9c030e68b09e | [log] [tgz] |
---|---|---|
author | Marcello Albano <[email protected]> | Tue Sep 13 16:42:45 2022 -0700 |
committer | Marcello Albano <[email protected]> | Wed Oct 12 17:39:29 2022 -0700 |
tree | ff4f5e746e96eee7584a1718125e677aafd209dc | |
parent | 1d966987be6795afd355d35ad13632620e43f335 [diff] |
Created ProfileVerifier to check whether a compilation profile exists The ProfileVerifier checks if a compilation profile is installed, either through play store, package manager or profile installer. A reference profile can be the result of either a baseline profile, a cloud profile or a bg dex opt. If a reference profile exists at the first app start or after an app update, this means that a baseline profile or a cloud profile was installed, since the bg dex opt happen later in background. The ProfileVerifier caches the result after the first app start to exclude bg dex opt and rechecks for reference profile only after app update. The same is applied also to current profiles, with the exception that the check for current profiles can be forced, in case the installation was done at a later time through ProfileInstallerReceiver. Test: ./gradlew profileinstaller:integration-tests:profile-verification:cC Bug: 246653809 Change-Id: I263a45582743afce0c3d9aefe629c07dfde77a72 Relnote: Added ProfileVerifier api to check whether a compilation profile exists for the app
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.