mirror of
https://github.com/pocket-id/pocket-id.git
synced 2026-02-05 00:39:38 +03:00
🐛 Bug Report: First passkey login attempt fails on Android, works after "Retry" #441
Reference in New Issue
Block a user
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?
Originally created by @rmb82 on GitHub (Aug 24, 2025).
Reproduction steps
When I try to log in using a passkey (WebAuthn) on my Android phone (Pixel 9 Pro XL, Android 16, Chrome):
Expected behavior
Authentication should succeed on the first attempt, right after passkey validation.
There should be no need to click "Retry" or restart the flow if the passkey is valid and the authentication completes normally.
Actual Behavior
The first authentication attempt fails with an error ("Something went wrong").
After clicking Retry, the login succeeds immediately — even without repeating the biometric step.
From the user's point of view:
📋 Relevant log from Pocket ID (v1.8.1):
Device info:
Pocket ID Version
v1.8.1 ( same on previously version)
Database
SQLite
OS and Environment
Debian12 / Docker (OMV Compose)
compose :
Log Output
@stonith404 commented on GitHub (Aug 24, 2025):
This seems like a bug of Android or Chrome because "Failed to lookup Client-side Discoverable Credential: record not found" means that Pocket ID can't find the provided passkey.
Does this happen every time your try to sign in? Can you try passkey authentication on another website to check if this really only happens with Pocket ID? Can you try it in another browser and device?
@rmb82 commented on GitHub (Aug 24, 2025):
I just tested on https://demo.pocket-id.org/start-demo and I didn’t experience any issue there.
@chuegel commented on GitHub (Aug 30, 2025):
Having the se issue on a Pixel 8 Pro. Although I'm running GrapheneOS and the browser is Vanadium. Other webauthn sites like Amazon, PayPal work
Edit: webauthn.io works as well
Demo shows the same issue
@rmb82 commented on GitHub (Sep 3, 2025):
Additional tests
On my own phone (Pixel 9 Pro XL, Android 16) with Brave: authentication works on the first try, no error shown.
On my wife’s Samsung S23 FE (Android, Chrome/Brave): authentication does not work at all.
➡️ Can you please confirm if Pocket ID is expected to work correctly with Android browsers and passkeys/biometric authentication?
@stonith404 commented on GitHub (Sep 9, 2025):
Does webauthn.io work as well if you set "User Verification" and "Discoverable Credential" to required? Please make sure to test it exactly the same way as in Pocket ID. E.g if you have created the passkey on a different device, register your account on webauthn.io on the other device as well.
@stonith404 commented on GitHub (Sep 22, 2025):
I’ll close this issue for now since there hasn’t been any recent activity. If you gather more details or try the experiment I shared earlier with webauthn.io, feel free to comment here and we can reopen the issue.
@mvantschip commented on GitHub (Oct 4, 2025):
Hi all,
Experiencing the exact same problem: on my phone/web browser, no issues at all, but my partner is unable to login. I checked webauthnio and it shows the following error on their (phone) Firefox browser when I click register:
"Type error for parameter updateProperties (Property "highlighted" is unsupported by Firefox) for tabs.update."
On my Firefox, there is no error. I also do not see any particular problems in pocketid logs.
We have the same phone and the same Firefox build, we both use Bitwarden for our passkeys.
Any other tests I could run to investigate the problem?
Thanks,
@stonith404 commented on GitHub (Oct 5, 2025):
@mvantschip Thanks for testing. If the issue happens on webauthn.io as well, it's not a bug that we can solve on our side. A quick search suggests that this issues is caused by Bitwarden (https://github.com/bitwarden/clients/issues/13798). Maybe your partner has an older version of Bitwarden installed?
@mvantschip commented on GitHub (Oct 6, 2025):
Thank you for the swift response. I also saw the Bitwarden issue. The weird thing is that my partner was on a newer version of Bitwarden than I was... Either way, will continue troubleshooting on their end then. Thanks again!