github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-07-11 00:53:29 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #6587] [PM-32771] Passkey authentication fails with "Passkeys not supported for this app" error in X (Twitter) #127744

New Issue
Open
opened 2026-06-13 21:05:46 -05:00 by GiteaMirror · 15 comments
GiteaMirror commented 2026-06-13 21:05:46 -05:00
Owner
Copy Link

Originally created by @oakencore on GitHub (Feb 26, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6587

Origin

Native Application (non-browser app)

Web URL or App name

X

Passkey Action

  • Creating new passkey (Registration)
  • Signing in (Authentication)

Build Information

Version 2026.2.0 (21203)

Additional Information

When attempting to sign into the X (Twitter) Android app using a passkey stored in Bitwarden, the error "Passkeys not supported for this app" is displayed immediately after Bitwarden is prompted.

Steps to reproduce:

  1. Have a passkey for X/Twitter saved in Bitwarden
  2. Open X app → Sign in → Sign in with passkey
  3. Bitwarden prompt appears, then shows "Passkeys not supported for this app"

The same passkey works on x.com in the browser.

X app version: 11.68.0

Related issues: #5322, #6164

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 @oakencore on GitHub (Feb 26, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6587 ### Origin Native Application (non-browser app) ### Web URL or App name X ### Passkey Action - [ ] Creating new passkey (Registration) - [x] Signing in (Authentication) ### Build Information Version 2026.2.0 (21203) ### Additional Information When attempting to sign into the X (Twitter) Android app using a passkey stored in Bitwarden, the error "Passkeys not supported for this app" is displayed immediately after Bitwarden is prompted. Steps to reproduce: 1. Have a passkey for X/Twitter saved in Bitwarden 2. Open X app → Sign in → Sign in with passkey 3. Bitwarden prompt appears, then shows "Passkeys not supported for this app" The same passkey works on x.com in the browser. X app version: 11.68.0 Related issues: #5322, #6164 ### 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-06-13 21:05:46 -05:00
GiteaMirror commented 2026-06-13 21:05:48 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 26, 2026):

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

<!-- gh-comment-id:3965089581 --> @bitwarden-bot commented on GitHub (Feb 26, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-32771](https://bitwarden.atlassian.net/browse/PM-32771) [PM-32771]: https://bitwarden.atlassian.net/browse/PM-32771?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-06-13 21:05:48 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 26, 2026):

Could you copy & paste in your details about the device etc. by going to Settings --> About --> Version in the BW Android app?

<!-- gh-comment-id:3965536099 --> @pamperer562580892423 commented on GitHub (Feb 26, 2026): Could you copy & paste in your details about the device etc. by going to Settings --> About --> Version in the BW Android app?
GiteaMirror commented 2026-06-13 21:05:48 -05:00
Author
Owner
Copy Link

@daniellbw commented on GitHub (Feb 26, 2026):

Hi there,

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

Thanks!

<!-- gh-comment-id:3965984771 --> @daniellbw commented on GitHub (Feb 26, 2026): Hi there, This issue has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2026-06-13 21:05:49 -05:00
Author
Owner
Copy Link

@oakencore commented on GitHub (Feb 28, 2026):

Could you copy & paste in your details about the device etc. by going to Settings --> About --> Version in the BW Android app?

© Bitwarden Inc. 2015-2026

Version: 2026.2.0 (21203)
📱 google Pixel 10 Pro 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2026.2-rc46@cbe13d2015f97955de1e0f11a229330ddd4654c0
💻 build source: bitwarden/android/actions/runs/21762978463/attempts/1
🦀 SDK: 2.0.0-4872-065ef30b
🌩 Server: 2026.2.0 @ US

<!-- gh-comment-id:3977302033 --> @oakencore commented on GitHub (Feb 28, 2026): > Could you copy & paste in your details about the device etc. by going to Settings --> About --> Version in the BW Android app? © Bitwarden Inc. 2015-2026 Version: 2026.2.0 (21203) 📱 google Pixel 10 Pro 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2026.2-rc46@cbe13d2015f97955de1e0f11a229330ddd4654c0 💻 build source: bitwarden/android/actions/runs/21762978463/attempts/1 🦀 SDK: 2.0.0-4872-065ef30b 🌩 Server: 2026.2.0 @ US
GiteaMirror commented 2026-06-13 21:05:49 -05:00
Author
Owner
Copy Link

@BabyOilJohnson commented on GitHub (Mar 24, 2026):

I'm having this issue too. ProtonPass works perfectly.

<!-- gh-comment-id:4118221861 --> @BabyOilJohnson commented on GitHub (Mar 24, 2026): I'm having this issue too. ProtonPass works perfectly.
GiteaMirror commented 2026-06-13 21:05:49 -05:00
Author
Owner
Copy Link

@shreyasbharath commented on GitHub (Apr 7, 2026):

Outlook on Android has the same issue

<!-- gh-comment-id:4202833452 --> @shreyasbharath commented on GitHub (Apr 7, 2026): Outlook on Android has the same issue
GiteaMirror commented 2026-06-13 21:05:50 -05:00
Author
Owner
Copy Link

@slux83 commented on GitHub (Apr 18, 2026):

Hi, same issue with kraken app. Works well with android browser (Brave)

<!-- gh-comment-id:4274612135 --> @slux83 commented on GitHub (Apr 18, 2026): Hi, same issue with kraken app. Works well with android browser (Brave)
GiteaMirror commented 2026-06-13 21:05:50 -05:00
Author
Owner
Copy Link

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

Hi, same issue with kraken app. Works well with android browser (Brave)

@slux83 As the reasons can differ, I would recommend to open a new "passkey bug issue" about the "Kraken" app. Document everything as best as you can.

<!-- gh-comment-id:4274694004 --> @pamperer562580892423 commented on GitHub (Apr 18, 2026): > Hi, same issue with kraken app. Works well with android browser (Brave) @slux83 As the reasons can differ, I would recommend to open a new "passkey bug issue" about the "Kraken" app. Document everything as best as you can.
GiteaMirror commented 2026-06-13 21:05:50 -05:00
Author
Owner
Copy Link

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

@oakencore @daniellbw Actually, I can't reproduce the current issue here.

I just created a test account on X for this.

After I created the X account:

  • I was not able to create (!) a login-passkey via the X app (the X app throws the following error message when the Bitwarden app gets invoked during the passkey registration process: "Request cancelled by X")
  • I was only able to create a login-passkey with the BW Android app via logging in to X in a mobile browser (Brave in my case - and I didn't test it on a desktop computer now)
  • but when I deleted the account info for X on Android, I was able to authenticate/sign-in to the X app with that passkey from my BW vault / the BW Android app

So, if anything, I see the opposite than the current issue here: sign-in with passkey works for the X app, but passkey-registration doesn't work with the X app.

© Bitwarden Inc. 2015-2026
Version: 2026.3.1 (21415)
📱 Fairphone FP5 🤖 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: 2026.4.0 @ EU

<!-- gh-comment-id:4274725362 --> @pamperer562580892423 commented on GitHub (Apr 18, 2026): @oakencore @daniellbw Actually, I can't reproduce the current issue here. I just created a test account on X for this. After I created the X account: - I was **not** able to create (!) a login-passkey via the X app (the X app throws the following error message when the Bitwarden app gets invoked during the passkey registration process: "Request cancelled by X") - I was only able to create a login-passkey with the BW Android app via logging in to X in a **mobile browser** (Brave in my case - and I didn't test it on a desktop computer now) - but when I deleted the account info for X on Android, I **was able** to authenticate/sign-in to the X app with that passkey from my BW vault / the BW Android app So, if anything, I see the opposite than the current issue here: sign-in with passkey works for the X **app**, but passkey-registration doesn't work with the X app. © Bitwarden Inc. 2015-2026 Version: 2026.3.1 (21415) 📱 Fairphone FP5 🤖 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: 2026.4.0 @ EU
GiteaMirror commented 2026-06-13 21:05:51 -05:00
Author
Owner
Copy Link

@ilsubyeega commented on GitHub (Apr 18, 2026):

@pamperer562580892423 hi, mind try to use x app from non-playstore(not installed from google play store, manually installed via apk etc)? i believe that is the reason

<!-- gh-comment-id:4274774687 --> @ilsubyeega commented on GitHub (Apr 18, 2026): @pamperer562580892423 hi, mind try to use x app from non-playstore(not installed from google play store, manually installed via apk etc)? i believe that is the reason
GiteaMirror commented 2026-06-13 21:05:51 -05:00
Author
Owner
Copy Link

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

mind try to use x app from non-playstore(not installed from google play store, manually installed via apk etc)?

@ilsubyeega I would do that with the X app. But I only found links to the Google Play Store on x.com. Is there even an official apk?

PS: Might also be relevant to know if @oakencore used the X app from Google Play Store - or from somewhere else.

<!-- gh-comment-id:4274803543 --> @pamperer562580892423 commented on GitHub (Apr 18, 2026): > mind try to use x app from non-playstore(not installed from google play store, manually installed via apk etc)? @ilsubyeega I would do that with the X app. But I only found links to the Google Play Store on x.com. Is there even an official apk? PS: Might also be relevant to know if @oakencore used the X app from Google Play Store - or from somewhere else.
GiteaMirror commented 2026-06-13 21:05:51 -05:00
Author
Owner
Copy Link

@ilsubyeega commented on GitHub (Apr 19, 2026):

Is there even an official apk?

I haven't seen a official apk distributed without google play store yet. Users will just download apk from unofficial way when google service wasnt capable in their devices.

I believe apk can be extracted via adb and then remove app from device, then reinstalling it.

<!-- gh-comment-id:4274879838 --> @ilsubyeega commented on GitHub (Apr 19, 2026): > Is there even an official apk? I haven't seen a official apk distributed without google play store yet. Users will just download apk from unofficial way when google service wasnt capable in their devices. I believe apk can be extracted via adb and then remove app from device, then reinstalling it.
GiteaMirror commented 2026-06-13 21:05:52 -05:00
Author
Owner
Copy Link

@CoffeePatch commented on GitHub (May 31, 2026):

Adding my report to this issue. I am experiencing the exact same behavior with the X (Twitter) Android app.
My steps:

  1. Passkey registration directly inside the X app fails.
  2. As a workaround, I successfully generated and saved the passkey via the Bitwarden web browser extension on my PC.
  3. However, when I try to authenticate/sign-in on the X Android app using that perfectly valid, saved passkey, Bitwarden intercepts the prompt but immediately throws the error: "Passkeys not supported for this app."

Note: I tested Proton Pass on the exact same device, and it was able to successfully create and use the passkey for X, indicating this is an issue specifically with how the Bitwarden Android app is communicating with the X app's API.

<!-- gh-comment-id:4587192629 --> @CoffeePatch commented on GitHub (May 31, 2026): Adding my report to this issue. I am experiencing the exact same behavior with the X (Twitter) Android app. **My steps:** 1. Passkey registration directly inside the X app fails. 2. As a workaround, I successfully generated and saved the passkey via the Bitwarden web browser extension on my PC. 3. However, when I try to authenticate/sign-in on the X Android app using that perfectly valid, saved passkey, Bitwarden intercepts the prompt but immediately throws the error: *"Passkeys not supported for this app."* **Note:** I tested Proton Pass on the exact same device, and it was able to successfully create and use the passkey for X, indicating this is an issue specifically with how the Bitwarden Android app is communicating with the X app's API.
GiteaMirror commented 2026-06-13 21:05:52 -05:00
Author
Owner
Copy Link

@MasterOfStar commented on GitHub (Jun 9, 2026):

indicating this is an issue specifically with how the Bitwarden Android app is communicating with the X app's API.

True
same bug on Backpack(app.backpack.mobile). I can't login with passkey. But other passkey manager is successul used.(such as Google)
Bitwarden's implementation of passkeys may be non-standard, or perhaps too standard (to the point of being incompatible with some "dirty" methods?).

<!-- gh-comment-id:4659196776 --> @MasterOfStar commented on GitHub (Jun 9, 2026): > indicating this is an issue specifically with how the Bitwarden Android app is communicating with the X app's API. True same bug on Backpack(app.backpack.mobile). I can't login with passkey. But other passkey manager is successul used.(such as Google) Bitwarden's implementation of passkeys may be non-standard, or perhaps too standard (to the point of being incompatible with some "dirty" methods?).
GiteaMirror commented 2026-06-13 21:05:52 -05:00
Author
Owner
Copy Link

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

same bug on Backpack(app.backpack.mobile)

@MasterOfStar You probably should report this separately here on the Android repository as a "Passkey Bug Report".

<!-- gh-comment-id:4659474582 --> @pamperer562580892423 commented on GitHub (Jun 9, 2026): > same bug on Backpack(app.backpack.mobile) @MasterOfStar You probably should report this separately here on the Android repository as a "Passkey Bug Report".
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#127744
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?