bitwarden / bitwarden/android

[PM-29479] Bitwarden Android app interferes with Google passkey reverification

Open
#6,250 7 comments 0 reactions 0 assignees View on GitHub
app:password-manager bug-passkey
Dominant language
Kotlin
Stars
9.4k
Forks
1.1k
Avg merge
1d 14h
Merged PRs (30d)
67

Description

### Origin

Native Application (non-browser app)

### Web URL or App name

google.com

### Passkey Action

- [ ] Creating new passkey (Registration)
- [x] Signing in (Authentication)

### Build Information

© Bitwarden Inc. 2015-2025

Version: 2025.11.1 (20994)
📱 samsung SM-A155F 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2025.11-rc39@63c4e1fe9314d2b2f2c0989b5bb8c265b3cbc57e
💻 build source: bitwarden/android/actions/runs/19583271293/attempts/2
🦀 SDK: 1.0.0-3436-2a00b727
🌩 Server: 2025.11.1 @ US

### Additional Information

**Steps to reproduce**

1. Install Bitwarden on Android and log in.
2. In Bitwarden app settings enable “Use Chrome autofill integration”, and in Chrome autofill settings, ensure that "Autofill using another service" is selected.
3. In Android passkeys & password settings, Google is also enabled as as an additional service (see screenshots).
4. Open Chrome and log in to a Google account using a passkey. Initial login works normally.
5. Click on the profile icon > Manage your Google account > Security & sign-in.
6. Perform any action that triggers identity reverification with a passkey (for example accessing or attempting to change a security setting).
7. The page switches to the reverification state and waits for a fingerprint prompt.
8. No fingerprint or passkey UI appears. The screen stays stuck on “Verifying it's you..."

**Expected result**

Chrome should show the Android biometric or passkey prompt and complete reverification.

**Actual result**

No biometric or passkey prompt appears. The page stays stuck on verifying.

**Additional notes**

Disabling “Use Chrome autofill integration” fixes the issue immediately.

Initial passkey login always works. Only reverification fails.

The issue happens regardless of where the passkey is stored.

**Screenshots**

Image

Image

Image

Image

### Issue Tracking Info

- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.