AlexT
May 28, 2026, 7:54am
1
Using BW on my Pixel 10 I am getting more and more prompts in mobile apps to define a PassKey (which is nice). If I confirm I get a Bitwarden unlock request (as expected) but then an error “Passkey not supported for this app”. Most recent exemples would be WhatsApp and Revolut.
What gives ?
The “Revolut” app is an open issue (and seems to be an issue on their side, if you read the comments):
opened 09:07AM - 13 Nov 25 UTC
app:password-manager
bug-passkey
### Origin
Native Application (non-browser app)
### Web URL or App name
Revol… ut (com.revolut.revolut)
### Passkey Action
- [x] Creating new passkey (Registration)
- [ ] Signing in (Authentication)
### Build Information
App Version: 2025.10.1 (20867)
Build: release/standard
Operating System: Android 16 (API 36)
Device: Samsung SM-A566E (Galaxy A56)
### Additional Information
**Related Issue:**
This appears similar to #6111, which was closed due to insufficient reproduction information.
I'm providing detailed logs, screenshots, and device information to help investigate this issue.
**Steps to reproduce:**
1. Open Revolut app (com.revolut.revolut)
2. Attempt to create a passkey
3. Bitwarden autofill appears
4. Error dialog displays: "An error has occurred - Passkeys not supported for this app"
**Observations:**
- Digital Asset Links verification succeeds (200 response)
- Revolut's certificate fingerprint is correctly verified
- Bitwarden autofill service processes the request (request ID 2254)
- Despite successful verification, passkey operation fails
**Attached:**
- Screenshot of error dialog 
- Application logs showing the autofill request flow [flight_recorder_2025-11-13_09-40-43.txt](https://github.com/user-attachments/files/23520767/flight_recorder_2025-11-13_09-40-43.txt)
### 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.
… and “WhatsApp” worked recently, but just a few minutes ago the corresponding bug report was reopened:
opened 02:04PM - 08 Jun 25 UTC
bug
app:password-manager
bug-passkey
### Steps To Reproduce
1. Go to 'WhatsApp, open settings and attempt to create … a passkey'
2. You will be prompted to save it to Bitwarden, do that
3. You will get an error from bitwarden (This app doesn't support passkey)
### Expected Result
It should create passkey for whatsapp as usual
### Actual Result
it returns error that the app doesn't support passkey
### Screenshots or Videos
_No response_
### Additional Context
_No response_
### Build Version
2025.5.0 (20269)
### What server are you connecting to?
US
### Self-host Server Version
_No response_
### Environment Details
© Bitwarden Inc. 2015-2025
Version: 2025.5.0 (20269)
📱 samsung SM-A145R 🤖 14@34 📦 prod
🧱 commit: https://github.com/bitwarden/android/commit/1e665db8aeb92989bdc7e312506cddd4887cde8e
💻 build source: bitwarden/android/actions/runs/15300207138/attempts/1
### 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.
So, in general passkeys should work with the Android app. If they don’t work at all, you should look into your configuration (a good way to test it, if you just started using passkeys on Android: it works without issue for me with my forum account here, so try that first). If it’s “only” certain apps: it may be a bug – or an issue “on the other side” (bad implementation), and in both cases, report those as “passkey issues” here: https://github.com/bitwarden/android/issues