github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #6775] [PM-34827] Passkey service does not fall-through when logged out. #50591

New Issue
Open
opened 2026-05-01 13:43:21 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-01 13:43:21 -05:00
Owner
Copy Link

Originally created by @craftxbox on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6775

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: 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

  • 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.
Originally created by @craftxbox on GitHub (Apr 9, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6775 ### 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 <details> <summary>Build Info</summary> © 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 </details> ### 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. <details> <summary>Flight Recorder</summary> ``` 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 ``` </details> ### 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.
GiteaMirror added the bug-passkeyapp:password-manager labels 2026-05-01 13:43:21 -05:00
GiteaMirror commented 2026-05-01 13:43:24 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Apr 9, 2026):

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

<!-- gh-comment-id:4214186664 --> @bitwarden-bot commented on GitHub (Apr 9, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-34827](https://bitwarden.atlassian.net/browse/PM-34827) [PM-34827]: https://bitwarden.atlassian.net/browse/PM-34827?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-05-01 13:43:27 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 9, 2026):

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"?

Image
<!-- gh-comment-id:4214290717 --> @pamperer562580892423 commented on GitHub (Apr 9, 2026): 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"? <img width="400" height="515" alt="Image" src="https://github.com/user-attachments/assets/e49da865-6777-4072-a40f-5e319518a56b" />
GiteaMirror commented 2026-05-01 13:43:29 -05:00
Author
Owner
Copy Link

@craftxbox commented on GitHub (Apr 9, 2026):

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!

<!-- gh-comment-id:4214402175 --> @craftxbox commented on GitHub (Apr 9, 2026): 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!
GiteaMirror commented 2026-05-01 13:43:30 -05:00
Author
Owner
Copy Link

@cbbit commented on GitHub (Apr 10, 2026):

Hi there,

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

Thanks!

<!-- gh-comment-id:4224284511 --> @cbbit commented on GitHub (Apr 10, 2026): Hi there, This report has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug-passkey
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#50591
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?