@algorandfoundation/react-native-passkey-autofill 1.0.0-canary.2 → 1.0.0-canary.20

package/.nvmrc

@@ -0,0 +1 @@
+22

package/.oxfmtrc.json

@@ -0,0 +1,4 @@
+{
+  "$schema": "./node_modules/oxfmt/configuration_schema.json",
+  "ignorePatterns": []
+}

package/.oxlintrc.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "./node_modules/oxlint/configuration_schema.json",
+  "plugins": ["eslint", "react", "react-perf", "typescript", "unicorn", "oxc"],
+  "categories": {
+    "correctness": "error"
+  },
+  "rules": {
+    "react-hooks/exhaustive-deps": "warn",
+    "eslint/no-unused-vars": "warn"
+  },
+  "env": {
+    "builtin": true
+  }
+}

package/.releaserc

@@ -0,0 +1,30 @@
+{
+  "branches": [
+    "release",
+    {
+      "name": "main",
+      "prerelease": "canary",
+      "channel": "next"
+    }
+  ],
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    "@semantic-release/changelog",
+    [
+      "@semantic-release/exec",
+      {
+        "prepareCmd": "pnpm fmt"
+      }
+    ],
+    "@semantic-release/npm",
+    [
+      "@semantic-release/git",
+      {
+        "assets": ["package.json", "pnpm-lock.yaml", "CHANGELOG.md"],
+        "message": "chore(release): ${nextRelease.version} \n\n${nextRelease.notes}"
+      }
+    ],
+    "@semantic-release/github"
+  ]
+}

package/ARCHITECTURE.md

@@ -35,9 +35,11 @@ The Android part is implemented using Kotlin and follows the Android Autofill Fr
 The `PasskeyAutofillCredentialProviderService` is the core of the Android implementation. It extends the Android Jetpack `CredentialProviderService` to provide passkeys directly to the system's Credential Manager.
 
 ##### What is `CredentialProviderService`?
+
 Introduced in Android 14 (API level 34) and backported to Android 9 via the Jetpack Credentials library, this service allows password managers and other credential providers to integrate with the system's unified sign-in flow. When a user interacts with a sign-in or sign-up field, the system queries registered services to provide available credentials.
 
 ##### Handling the Chain of Trust
+
 The "Chain of Trust" ensures that passkeys are only used by the legitimate owners of a domain or application. This is handled through several layers of validation:
 
 1.  **Digital Asset Links**: For a passkey to be used across a website and an Android app, the website must host a `/.well-known/assetlinks.json` file that explicitly authorizes the Android app (via its package name and certificate fingerprint). This establishes a cryptographically verified link between the web origin and the mobile application.
@@ -61,7 +63,13 @@ The following methods are exposed to the JavaScript layer:
 - `getHdRootKeyId()`: Retrieves the current HD root key ID.
 - `configureIntentActions(getPasskeyAction: string, createPasskeyAction: string)`: Configures the intent actions used for Passkey flows.
 - `clearCredentials()`: Clears all stored credentials.
+- `isProviderActive()`: Returns `true` if this app is the user-selected system credential/autofill provider. Uses Android's `Settings.Secure("credential_service"[_primary])` (API 34+) and iOS's `ASCredentialIdentityStore.getState`. Useful both for gating passkey UI at runtime and for E2E tests, which need to confirm that an OS passkey prompt is served by _this_ provider rather than any other installed one.
+- `openProviderSettings()`: Deep-links the user to the OS credential/autofill provider settings so they can enable this app as the active provider. Resolves to `true` if a settings screen could be launched.
 
 ## Security Considerations
 
 As this module handles sensitive information (Passkeys), it is crucial to ensure that keys and secrets are handled securely in the native layers. Master keys should be stored in secure storage (like Android Keystore or iOS Keychain).
+
+## End-to-End Tests
+
+The `e2e/` workspace drives the `example/` app with Appium 2 + WebdriverIO, executed through Jest. The Android job uses the UiAutomator2 driver; the iOS job uses XCUITest. The happy-path spec mirrors the example and exercises passkey registration and assertion against `https://debug.liquidauth.com`. See [`e2e/README.md`](./e2e/README.md) for local usage and the [`E2E` workflow](./.github/workflows/e2e.yml) for CI.

package/CHANGELOG.md

@@ -0,0 +1,108 @@
+# [1.0.0-canary.20](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.19...v1.0.0-canary.20) (2026-06-10)
+
+### Bug Fixes
+
+- **Android:** improve setting intent handling, gradle includes pickFirst for MMKV. ([27af9e4](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/27af9e470fb2d53f375422b246e3f8d72329b2c0))
+
+# [1.0.0-canary.19](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.18...v1.0.0-canary.19) (2026-06-09)
+
+### Bug Fixes
+
+- **android:** credential repository filter types in getAllCredentials ([2b6523f](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/2b6523fc25aaadb5152b0b0d3d6b3a56e9de1759))
+
+# [1.0.0-canary.18](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.17...v1.0.0-canary.18) (2026-06-09)
+
+### Features
+
+- PRF extension support for deterministically derived secrets ([4b5b05a](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/4b5b05ab146e39b191855ccb01fd4aca5ed32819))
+
+# [1.0.0-canary.17](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.16...v1.0.0-canary.17) (2026-05-28)
+
+### Bug Fixes
+
+- allow configurable AAGUID ([d5a8176](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/d5a81765ba150e9873e18875f0ac9f7bc4aede93))
+- **Android:** add NoOp methods for iOS-specific functionality ([e2c64db](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/e2c64db479cda70c7c61b7ab3021b70db949a15b))
+- compile issue ([16b939c](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/16b939cb555e75bd052ce57a41a838810a2770cd))
+
+### Features
+
+- configurable credential requirement ([dc09916](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/dc09916d1ee5c8c9d33e53b57f00171472f4f665))
+- record lastUsedAt/count and fix error handling ([47b40ab](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/47b40abf692c0f7cffee6f2266c66f61f8006a65))
+
+# [1.0.0-canary.16](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.15...v1.0.0-canary.16) (2026-05-15)
+
+### Bug Fixes
+
+- align ios autofill root key flow ([1287f57](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/1287f57952b41829032ef368bad826624375e9a3))
+
+### Features
+
+- add iOS passkey autofill provider ([9aad8f8](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/9aad8f8ceb2ad54cf53847b60dd6e70d5b2a1f2b))
+
+# [1.0.0-canary.15](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.14...v1.0.0-canary.15) (2026-04-10)
+
+### Bug Fixes
+
+- use bouncycastle bcprov-jdk15to18 for android ([cd860b2](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/cd860b2012f2189e854137afa55c7a0c0dc1b94c))
+
+# [1.0.0-canary.14](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.13...v1.0.0-canary.14) (2026-04-10)
+
+### Bug Fixes
+
+- switch to maven for local AAR dependency ([f4e52b4](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/f4e52b46d618e6e8a7972e649c5d75d768e32339))
+
+# [1.0.0-canary.13](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.12...v1.0.0-canary.13) (2026-04-10)
+
+### Bug Fixes
+
+- bump keystore to 1.0.0-canary.9 ([f093bab](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/f093bab0b74d5cbf93e8f03ecd8d56c77597d3f5))
+
+# [1.0.0-canary.12](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.11...v1.0.0-canary.12) (2026-04-10)
+
+### Features
+
+- **android:** biometrics single tap and fallback ([a6cbe4c](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/a6cbe4cf51579b15b2a219e1e06e843bb6001ed4))
+- **android:** support DER format ([492034f](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/492034f8b031e795b2575be69da8c3a1adb9096c))
+
+# [1.0.0-canary.11](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.10...v1.0.0-canary.11) (2026-03-31)
+
+### Bug Fixes
+
+- update service url ([ffc2c22](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/ffc2c22e18661cf5a159eef5b06303b94981df6b))
+
+# [1.0.0-canary.10](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.9...v1.0.0-canary.10) (2026-03-30)
+
+### Bug Fixes
+
+- bouncy castle provider insertion order ([9e9039d](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/9e9039deab02f75f5a4397cedc098c0ca2e24875))
+
+# [1.0.0-canary.9](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.8...v1.0.0-canary.9) (2026-03-30)
+
+### Bug Fixes
+
+- x logins, refactor example views to be dialogs ([e7a1ccf](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/e7a1ccf91f88b5c369ff3082f06d538fc8b3db89))
+
+# [1.0.0-canary.8](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.7...v1.0.0-canary.8) (2026-03-27)
+
+### Features
+
+- passkey added and authenticated events ([b9871f4](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/b9871f475a9a633ae98d30a702ef2814ec8ae5e0))
+
+# [1.0.0-canary.7](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.6...v1.0.0-canary.7) (2026-03-24)
+
+### Bug Fixes
+
+- update package lock and include in CI/CD ([1d775cd](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/1d775cdde170a6ef400a1ee8a01fce759ddb1f1e))
+
+# [1.0.0-canary.6](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.5...v1.0.0-canary.6) (2026-03-24)
+
+### Bug Fixes
+
+- include banner for package README ([60a6559](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/60a655932faac6de57daf0f30261f2d03a2c1476))
+
+# [1.0.0-canary.5](https://github.com/algorandfoundation/react-native-passkey-autofill/compare/v1.0.0-canary.4...v1.0.0-canary.5) (2026-03-24)
+
+### Features
+
+- **android:** add allowed credentials mapping ([e7134fc](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/e7134fc1e5bf09649155e38010e4ef9728580812))
+- **android:** credential compatibility with system-provided clientDataHash and compact JSON ([428e96f](https://github.com/algorandfoundation/react-native-passkey-autofill/commit/428e96f89b73cd35fdbfaa6669f39da68403e17e))

package/CONTRIBUTING.md

@@ -10,11 +10,11 @@ To get started with the project, follow these steps:
 2. **Clone the repository** to your local machine.
 3. **Install dependencies** at the root of the project:
    ```bash
-   npm install
+   pnpm install
    ```
 4. **Build the project**:
    ```bash
-   npm run build
+   pnpm run build
    ```
 
 ## Development Workflow
@@ -29,7 +29,7 @@ The project includes an example app in the `example/` directory. You can use it
    ```
 2. Install example dependencies:
    ```bash
-   npm install
+   pnpm install
    ```
 3. Prebuild the example for Android or iOS:
    ```bash
@@ -37,9 +37,9 @@ The project includes an example app in the `example/` directory. You can use it
    ```
 4. Run the example app:
    ```bash
-   npm run android # for Android
+   pnpm run android # for Android
    # or
-   npm run ios # for iOS
+   pnpm run ios # for iOS
    ```
 
 ### Code Style
@@ -50,6 +50,16 @@ The project includes an example app in the `example/` directory. You can use it
 
 For more details on how the project is structured, see the [Architecture Guide](./ARCHITECTURE.md).
 
+### Testing
+
+Before submitting a Pull Request, ensure that both JavaScript and Native tests pass:
+
+```bash
+pnpm run test:all
+```
+
+For more details on the testing strategy, refer to the [Testing section in README.md](./README.md#🧪-testing).
+
 ## Submitting a Pull Request
 
 1. Create a new branch for your feature or bugfix:

package/README.md

@@ -1,15 +1,21 @@
-# 🔑 react-native-passkey-autofill
+# @algorandfoundation/react-native-passkey-autofill
 
-Passkey AutoFill for React Native using DP256.
+<p align="center">
+  <img src="https://raw.githubusercontent.com/algorandfoundation/react-native-passkey-autofill/refs/heads/main/assets/banner.png" width="100%" />
+</p>
+
+<p align="center">
+  Passkey AutoFill for React Native using DP256.
+</p>
 
 # 🚀 Get Started
 
 For bare React Native projects, you must ensure that you have [installed and configured the `expo` package](https://docs.expo.dev/bare/installing-expo-modules/) before continuing.
 
-### Add the package to your npm dependencies
+### Add the package to your dependencies
 
 ```bash
-npm install react-native-passkey-autofill
+pnpm add @algorandfoundation/react-native-passkey-autofill
 ```
 
 ### Configure for Android
@@ -25,7 +31,7 @@ If you are using Expo, you can configure the plugin in your `app.json` or `app.c
   "expo": {
     "plugins": [
       [
-        "react-native-passkey-autofill",
+        "@algorandfoundation/react-native-passkey-autofill",
         {
           "site": "https://your-fido-server.com",
           "label": "My Custom Credential Provider"
@@ -36,13 +42,78 @@ If you are using Expo, you can configure the plugin in your `app.json` or `app.c
 }
 ```
 
-- `site`: The URL of your FIDO server (default: `https://fido.shore-tech.net`).
+- `site`: The URL of your FIDO server (default: `https://debug.liquidauth.com`).
 - `label`: The name of the credential provider as it appears in Android settings (default: `My Credential Provider`).
+- `aaguid`: Optional authenticator AAGUID (UUID string) embedded in attestation responses to identify your authenticator to relying parties. When omitted, iOS uses the module's built-in default and Android uses the all-zero AAGUID emitted by the platform. Set the same value across all your apps (iOS, Android, web) so they present one identity.
+- `biometricRequirement`: Controls which authenticators satisfy passkey user verification. See [Biometric Requirement](#biometric-requirement) below.
+
+#### Biometric Requirement
+
+`biometricRequirement` is an optional string property that controls which authenticators are accepted for user verification during passkey creation and authentication.
+
+| Value                          | Android                                                                                  | iOS                                 |
+| ------------------------------ | ---------------------------------------------------------------------------------------- | ----------------------------------- |
+| `strong`                       | Strong biometric only                                                                    | Biometrics only (passcode rejected) |
+| `strongOrCredential` (default) | Strong biometric or device PIN/pattern/password                                          | Biometrics or device passcode       |
+| `weakOrCredential`             | Weak biometric or device credential (key is **not** crypto-bound — a security trade-off) | Biometrics or device passcode       |
+
+**Notes:**
+
+- Android cannot gate a hardware-backed key on weak biometrics, so `weakOrCredential` stores the key without user-authentication binding and uses the biometric prompt as a UI gate only. Use it only when you accept that trade-off.
+- The default `strongOrCredential` is more permissive than the previous strong-only behavior; integrators upgrading will additionally allow the device credential on Android (iOS behavior is unchanged).
+
+### Configure for iOS
+
+iOS passkey AutoFill requires a Credential Provider extension, an App Group shared between the app and extension, and an associated domain for Web Credentials. The Expo config plugin can create and wire the extension during prebuild:
+
+```json
+{
+  "expo": {
+    "ios": {
+      "bundleIdentifier": "com.example.wallet",
+      "associatedDomains": ["webcredentials:your-fido-server.com"],
+      "entitlements": {
+        "com.apple.developer.authentication-services.autofill-credential-provider": true
+      }
+    },
+    "plugins": [
+      [
+        "@algorandfoundation/react-native-passkey-autofill",
+        {
+          "site": "https://your-fido-server.com",
+          "label": "My Custom Credential Provider",
+          "appGroup": "group.com.example.wallet.passkey-autofill",
+          "appleTeamId": "YOUR_TEAM_ID"
+        }
+      ]
+    ]
+  }
+}
+```
+
+For iOS integration, make sure that:
+
+- The app and Credential Provider extension both have the AutoFill Credential Provider capability.
+- The app and extension both have the same App Group entitlement.
+- The app has a `webcredentials:<domain>` associated domain, and that domain serves a valid `apple-app-site-association` file for the app identifier.
+- The deployment target is iOS 17 or newer for passkey credential provider support.
+- The generated extension target can link `AuthenticationServices.framework`, `CryptoKit.framework`, `MMKVCore`, and the deterministic P-256 Swift package.
+- `NSFaceIDUsageDescription` is present when biometric authentication is used.
+
+At runtime, the app must provide the native side with the master key, identify the HD root key stored in MMKV, and keep the iOS identity store in sync:
+
+```typescript
+await ReactNativePasskeyAutofill.setMasterKey(masterKeyHex);
+await ReactNativePasskeyAutofill.setHdRootKeyId(hdRootKeyId);
+await ReactNativePasskeyAutofill.refreshCredentialIdentities();
+```
+
+Call `refreshCredentialIdentities()` after creating, importing, deleting, or restoring passkeys so iOS AutoFill sees the current credentials.
 
 ## Usage
 
 ```typescript
-import ReactNativePasskeyAutofill from '@algorandfoundation/react-native-passkey-autofill';
+import ReactNativePasskeyAutofill from "@algorandfoundation/react-native-passkey-autofill";
 
 // 1. Set the master key for encryption (hex string)
 await ReactNativePasskeyAutofill.setMasterKey(masterKeyHex);
@@ -52,25 +123,93 @@ await ReactNativePasskeyAutofill.setHdRootKeyId(hdRootKeyId);
 
 // 3. Configure intent actions for the Passkey flows
 await ReactNativePasskeyAutofill.configureIntentActions(
-  'your.package.name.GET_PASSKEY',
-  'your.package.name.CREATE_PASSKEY'
+  "your.package.name.GET_PASSKEY",
+  "your.package.name.CREATE_PASSKEY",
 );
 
 // Optional: Clear credentials
 await ReactNativePasskeyAutofill.clearCredentials();
 ```
 
+## Events
+
+You can listen for events emitted by the native module when a passkey is successfully added or authenticated.
+
+```typescript
+import ReactNativePasskeyAutofill from "@algorandfoundation/react-native-passkey-autofill";
+import { useEffect } from "react";
+
+// ... inside a component or hook
+useEffect(() => {
+  const addedSubscription = ReactNativePasskeyAutofill.addListener("onPasskeyAdded", (event) => {
+    console.log("Passkey added successfully:", event.success);
+  });
+
+  const authSubscription = ReactNativePasskeyAutofill.addListener(
+    "onPasskeyAuthenticated",
+    (event) => {
+      console.log("Passkey authenticated successfully:", event.success);
+    },
+  );
+
+  return () => {
+    addedSubscription.remove();
+    authSubscription.remove();
+  };
+}, []);
+```
+
+## 🧪 Testing
+
+The project is set up with a comprehensive testing approach covering both JavaScript and Native (Kotlin) sides.
+
+### JavaScript Tests
+
+Run unit tests for the TypeScript module using Jest:
+
+```bash
+pnpm test
+```
+
+### Native Android Tests
+
+Run unit tests for the Kotlin code using JUnit and Robolectric. These tests are executed via the example app's Gradle wrapper:
+
+```bash
+pnpm run test:android
+```
+
+### All Tests
+
+Run both JS and Native tests:
+
+```bash
+pnpm run test:all
+```
+
+### Continuous Integration (CI)
+
+The project includes a GitHub Actions workflow that automatically runs linting, JS tests, and Native Android tests on every push and pull request to the `main` or `release` branches. You can find the configuration in `.github/workflows/ci.yml`.
+
+### Integration Testing (E2E)
+
+Full end-to-end tests driving the example app with Appium and WebdriverIO are available in the [`e2e/`](./e2e) directory. These tests exercise the entire passkey creation and usage flow on Android emulators and iOS simulators. See the [E2E README](./e2e/README.md) for more details.
+
+## 📱 Example App
+
+The [example](./example) app demonstrates how to integrate this module with a full wallet implementation.
+
 # 🤝 Contributing
 
 Contributions are very welcome! Please refer to guidelines described in the [contributing guide](./CONTRIBUTING.md).
 
 # 💖 Acknowledgements
 
-This has been the commination of many different efforts and ideas. We would like to thank the following individuals and organizations for their contributions:
+This has been the culmination of many different efforts and ideas. We would like to thank the following individuals and organizations for their contributions:
 
 - [Bruno Martins](https://github.com/bmartins) the architect at [Algorand Foundation](https://github.com/algorandfoundation) for conceptualizing and guiding the project.
 - [HashMapsData2Value](https://github.com/HashMapsData2Value) for his guidance and support in DP256 and XHD and his work on the native autofill libraries.
-- [Will Beaumont](https://github.com/mjbeau) for working though integration within the Pera wallet
+- [Will Beaumont](https://github.com/mjbeau) for working through integration within the Pera wallet
 - [Michael T Chuang](https://github.com/michaeltchuang) for his work in KMP integrations and client libraries.
 
 # 📄 License

package/android/build.gradle

@@ -27,6 +27,7 @@ if (useManagedAndroidSdkVersions) {
     defaultConfig {
       minSdkVersion safeExtGet("minSdkVersion", 24)
       targetSdkVersion safeExtGet("targetSdkVersion", 36)
+      testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
     }
   }
 }
@@ -43,26 +44,48 @@ android {
   kotlinOptions {
     freeCompilerArgs += ["-opt-in=kotlin.time.ExperimentalTime", "-opt-in=kotlin.RequiresOptIn"]
   }
+  testOptions {
+    unitTests.includeAndroidResources = true
+    // Let unmocked android.jar calls (e.g. android.util.Log) return defaults instead of throwing
+    // "Stub!" in JVM unit tests.
+    unitTests.returnDefaultValues = true
+  }
+  packagingOptions {
+    pickFirst '**/libc++_shared.so'
+    pickFirst '**/libmmkv.so'
+  }
+}
+
+repositories {
+  maven {
+    url = uri("file://${projectDir}/libs/repo")
+  }
 }
 
 dependencies {
-  implementation "androidx.credentials:credentials:1.3.0"
-  implementation "androidx.credentials:credentials-play-services-auth:1.3.0"
+  implementation "androidx.biometric:biometric-ktx:1.2.0-alpha05"
+  implementation "androidx.credentials:credentials:1.5.0-rc01"
+  implementation "androidx.credentials:credentials-play-services-auth:1.5.0-rc01"
   implementation "androidx.appcompat:appcompat:1.7.0"
   implementation "androidx.activity:activity-ktx:1.8.2"
   implementation "androidx.lifecycle:lifecycle-viewmodel-ktx:2.8.4"
   implementation "androidx.lifecycle:lifecycle-runtime-ktx:2.8.4"
   implementation "io.github.zhongwuzw:mmkv:2.3.0"
-  implementation "org.bouncycastle:bcprov-jdk18on:1.78.1"
+  implementation "org.bouncycastle:bcprov-jdk15to18:1.78.1"
   implementation "androidx.datastore:datastore-preferences:1.1.1"
-  implementation(name: 'dP256Android-release', ext: 'aar')
+  implementation "co.algorand:dP256Android:1.0.0"
   implementation fileTree(dir: 'libs', include: ['*.jar'])
   implementation "org.jetbrains.kotlinx:kotlinx-coroutines-android:1.8.0"
   implementation "org.jetbrains.kotlinx:kotlinx-coroutines-core:1.8.0"
-}
 
-repositories {
-  flatDir {
-    dirs 'libs'
-  }
-}
+  // Testing dependencies
+  testImplementation "junit:junit:4.13.2"
+  testImplementation "org.robolectric:robolectric:4.11.1"
+  testImplementation "io.mockk:mockk:1.13.8"
+  testImplementation "org.jetbrains.kotlinx:kotlinx-coroutines-test:1.8.0"
+
+  androidTestImplementation "androidx.test:runner:1.5.2"
+  androidTestImplementation "androidx.test:rules:1.5.0"
+  androidTestImplementation "androidx.test.ext:junit:1.1.5"
+  androidTestImplementation "androidx.test.espresso:espresso-core:3.5.1"
+}

package/android/libs/repo/co/algorand/dP256Android/1.0.0/dP256Android-1.0.0.pom

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+  <modelVersion>4.0.0</modelVersion>
+  <groupId>co.algorand</groupId>
+  <artifactId>dP256Android</artifactId>
+  <version>1.0.0</version>
+  <packaging>aar</packaging>
+</project>

package/android/src/main/AndroidManifest.xml

@@ -1,12 +1,12 @@
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
           xmlns:tools="http://schemas.android.com/tools">
+    <uses-permission android:name="android.permission.USE_BIOMETRIC"/>
     <application>
         <service
             android:name=".service.PasskeyAutofillCredentialProviderService"
             android:enabled="true"
             android:exported="true"
             android:label="@string/passkey_autofill_label"
-            android:icon="@mipmap/ic_launcher"
             android:permission="android.permission.BIND_CREDENTIAL_PROVIDER_SERVICE"
             tools:targetApi="upside_down_cake">
             <intent-filter>
@@ -16,13 +16,19 @@
                 android:name="android.credentials.provider"
                 android:resource="@xml/provider" />
         </service>
-        <activity android:name=".GetPasskeyActivity" android:exported="true">
+        <activity android:name="co.algorand.passkeyautofill.GetPasskeyActivity" 
+            android:exported="true" 
+            android:launchMode="singleTop"
+            android:theme="@style/Theme.PasskeyAutofill.Dialog">
             <intent-filter>
                 <action android:name="co.algorand.passkeyautofill.GET_PASSKEY"/>
                 <category android:name="android.intent.category.DEFAULT"/>
             </intent-filter>
         </activity>
-        <activity android:name=".CreatePasskeyActivity" android:exported="true">
+        <activity android:name="co.algorand.passkeyautofill.CreatePasskeyActivity" 
+            android:exported="true" 
+            android:launchMode="singleTop"
+            android:theme="@style/Theme.PasskeyAutofill.Dialog">
             <intent-filter>
                 <action android:name="co.algorand.passkeyautofill.CREATE_PASSKEY"/>
                 <category android:name="android.intent.category.DEFAULT"/>