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

[craftxbox]

Origin

Web (Browser)

Web URL or App name

Not applicable

Passkey Action

• Creating new passkey (Registration)
• 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: c2ef20e
💻 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

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

[bitwarden-bot]

Thank you for your report! We've added this to our internal board for review.
ID: PM-34827

[pamperer562580892423]

Another user here.

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.

Isn't that kind of expected, when you only select Bitwarden in the Android settings?!

Did you try to add Google as "Additional Service"?

[craftxbox]

I did add Google as a secondary as a workaround. The annoying part about that is it always attempts to "upsell" you on adding passkeys to it, and interrupts the system ui with another tap even if it has no passkey itself.

This is not expected because the system ui is supposed to be perfectly fine for handling NFC/USB/remote tokens (I use a yubikey), which is not within the purview of the Google auto fill service!

[cbbit]

Hi there,

This report has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!