commit | f6b9bdea083e7b6ba8d74fd373c826a951960b77 | [log] [tgz] |
---|---|---|
author | Curtis Belmonte <curtislb@google.com> | Mon Jul 01 10:35:24 2019 -0700 |
committer | Curtis Belmonte <curtislb@google.com> | Tue Jul 02 09:39:06 2019 -0700 |
tree | 4cd2498bf26f9c896b71764d3fcbfcc574566594 | |
parent | 29121e3812cac95cb8c45850f12f3ffe6aaf6bc9 [diff] |
Add fragment-specific constructor for biometric prompt Currently, constructing an instance of the androidx support biometric prompt requires a FragmentActivity. This is because BiometricPrompt relies on the activity internally for performing fragment transactions and checking for configuration changes. However, this is causing a crash when attempting to attach the biometric fragment to the activity via its fragment manager. This commit addresses the issue by adding a new constructor for BiometricPrompt which accepts a Fragment instead of a FragmentActivity. Then, when performing fragment transactions, BiometricPrompt can use the child fragment manager of the fragment instead of the activity's fragment manager. Checking for configuration changes is now handled by calling the appropriate method on the fragment's host activity (if one exists). This commit also updates the existing biometric prompt demo app to use the new constructor when the biometric prompt is hosted in a Fragment, rather than directly in a FragmentActivity. Test: Tested manually using biometric prompt demo app: 1. Repro the crash by changing the authenticate button to show a custom DialogFragment that launches BiometricPrompt during onResume 2. Re-run app with changes from this commit, and verify crash no longer repros 3. Verify that all authentication flows work as before when launched from the DialogFragment, including across configuration changes 4. Verify that the user can dismiss the DialogFragment without error and that backgrounding the app cancels authentication and dismisses prompt Fixes: 131980596 Change-Id: I2f868460ab6f81e3a848a89d61b76a97a5d5043e
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.
We are not currently accepting new modules.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
repo
(Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see the Repo Command Reference)mkdir ~/bin PATH=~/bin:$PATH curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo
git config --global user.name "Your Name" git config --global user.email "you@example.com"
mkdir androidx-master-dev cd androidx-master-dev
repo
command to initialize the repository.repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
To open the project with the specific version of Android Studio recommended for developing:
cd path/to/checkout/frameworks/support/ ./studiow
and accept the license agreement when prompted. Now you're ready edit, run, and test!
If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.
If you see any warnings (red underlines) run Build > Clean Project
.
You can do most of your work from Android Studio, however you can also build the full AndroidX library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
You can build maven artifacts locally, and test them directly in your app:
./gradlew createArchive
And put in your project build.gradle
file:
handler.maven { url '/path/to/checkout/out/androidx/build/support_repo/' }
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.
Run FooBarTest
Run androidx.foobar
The AndroidX repository has a set of Android applications that exercise AndroidX code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
These applications are named either <libraryname>-integration-tests-testapp
, or support-\*-demos
(e.g. support-4v-demos
or support-leanback-demos
). You can run them by clicking Run > Run ...
and choosing the desired application.
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
cd path/to/checkout/frameworks/support/ repo start my_branch_name . (make needed modifications) git commit -a repo upload --current-branch .
If you see the following prompt, choose always
:
Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?
If the upload succeeds, you'll see output like:
remote: remote: New Changes: remote: https://android-review.googlesource.com/c/platform/frameworks/support/+/720062 Further README updates remote:
To edit your change, use git commit --amend
, and re-upload.
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.