bitwarden / bitwarden/android

[PM-34827] Passkey service does not fall-through when logged out.

Open
#6,775 4 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

Web (Browser)

### Web URL or App name

Not applicable

### Passkey Action

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

### Build Information

Installed via Play store,
LineageOS 22.1 with MindTheGapps

Build Info
© Bitwarden Inc. 2015-2026

Version: 2026.3.1 (21415)
📱 google Pixel 3 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2026.3-rc49@c2ef20e1ed74a9cba60b19d5849af168629d3756
💻 build source: bitwarden/android/actions/runs/23660459640/attempts/1
🦀 SDK: 2.0.0-5676-14521973
🌩 Server: Vaultwarden 2025.12.0

### Additional Information

When Bitwarden is selected in android settings as the *only* auto fill provider, and an account is not yet signed in, Fido2 requests fail entirely **systemwide** as it appears Bitwarden does not attempt to invoke the system passkey UI as a fallback.
> [!NOTE]
> If it is involving the system ui, perhaps this is a LineageOS bug, however, I didnt see anything relevant in logcat at all to suggest this.

Flight Recorder

```
Bitwarden Android - Password Manager
Log Start Time: 2026-04-09 09:27:47:583
Log Duration: 1h
App Version: 2026.3.1 (21415)
Build: release/standard
SDK Version: 🦀 2.0.0-5676-14521973
CI Build Info: 🧱 commit: bitwarden/android/release/2026.3-rc49@c2ef20e1ed74a9cba60b19d5849af168629d3756
💻 build source: bitwarden/android/actions/runs/23660459640/attempts/1
Device: 📱 google Pixel 3 🤖 15@35 📦 prod
🌩 Server: Vaultwarden 2025.12.0
Fingerprint: google/blueline/blueline:12/SP1A.210812.016.C2/8618562:user/release-keys
2026-04-09 09:27:47:596 – DEBUG – lc7 – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.PreAuth in com.x8bit.bitwarden.ui.auth.feature.auth.AuthGraphRoute
2026-04-09 09:27:51:357 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded
2026-04-09 09:28:04:100 – WARNING – BitwardenCredentialProviderService – No active user. Cannot get credentials.
2026-04-09 09:28:04:100 – DEBUG – BitwardenCredentialProviderService – Get credential request received.
2026-04-09 09:28:13:294 – WARNING – BitwardenCredentialProviderService – No active user. Cannot get credentials.
2026-04-09 09:28:13:294 – DEBUG – BitwardenCredentialProviderService – Get credential request received.
2026-04-09 09:28:19:487 – DEBUG – ae – Network status change: Wifi(strength=FAIR)
2026-04-09 09:28:20:001 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded
```

### 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.