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

[GH-ISSUE #4239] Passkey support with UBank #50139

New Issue
Closed
opened 2026-05-01 11:39:01 -05:00 by GiteaMirror · 22 comments
GiteaMirror commented 2026-05-01 11:39:01 -05:00
Owner
Copy Link

Originally created by @Molenaar2 on GitHub (Nov 6, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4239

Steps To Reproduce

I have two accounts for my UBank app, both accounts have a passkey defined. One account sits in my own vault, the other account sits in the organisation I belong to.

When I try to log in to the app, I get an error that the passkey operation failed, because the user could not be verified. In the previous non-native version of Bitwarden I got a pop-up showing the two passkeys (unfortunately not the user IDs!) and I could select the passkey/account I wanted to use. With the new native version, due to the error, I can no longer login.

Expected Result

Logged in to banking app

Actual Result

Error message that passkey operation failed because user could not be verified

Screenshots or Videos

My banking app doesn't allow to make screenshots

Additional Context

The non native version showed a pop-up with three two passkeys and I could select the one to be used (note, it showed the passkeys, unfortunately not the user IDs) Now in the native version it gives an error.

Build Version

2024.10.2

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Samsung Galaxy A34
Android 14

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 @Molenaar2 on GitHub (Nov 6, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4239 ### Steps To Reproduce I have two accounts for my UBank app, both accounts have a passkey defined. One account sits in my own vault, the other account sits in the organisation I belong to. When I try to log in to the app, I get an error that the passkey operation failed, because the user could not be verified. In the previous non-native version of Bitwarden I got a pop-up showing the two passkeys (unfortunately not the user IDs!) and I could select the passkey/account I wanted to use. With the new native version, due to the error, I can no longer login. ### Expected Result Logged in to banking app ### Actual Result Error message that passkey operation failed because user could not be verified ### Screenshots or Videos My banking app doesn't allow to make screenshots ### Additional Context The non native version showed a pop-up with three two passkeys and I could select the one to be used (note, it showed the passkeys, unfortunately not the user IDs) Now in the native version it gives an error. ### Build Version 2024.10.2 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Samsung Galaxy A34 Android 14 ### 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 label 2026-05-01 11:39:01 -05:00
GiteaMirror commented 2026-05-01 11:39:05 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Nov 6, 2024):

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

<!-- gh-comment-id:2459423831 --> @bitwarden-bot commented on GitHub (Nov 6, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-14534
GiteaMirror commented 2026-05-01 11:39:05 -05:00
Author
Owner
Copy Link

@Felitendo commented on GitHub (Nov 10, 2024):

Same issue for me. I can login with passkeys, but I can't create them

<!-- gh-comment-id:2466938965 --> @Felitendo commented on GitHub (Nov 10, 2024): Same issue for me. I can login with passkeys, but I can't create them
GiteaMirror commented 2026-05-01 11:39:05 -05:00
Author
Owner
Copy Link

@Molenaar2 commented on GitHub (Nov 10, 2024):

Duplicate of #3866, will close this one

<!-- gh-comment-id:2466970055 --> @Molenaar2 commented on GitHub (Nov 10, 2024): Duplicate of #3866, will close this one
GiteaMirror commented 2026-05-01 11:39:06 -05:00
Author
Owner
Copy Link

@BJReplay commented on GitHub (Nov 11, 2024):

@Molenaar2 I think you should consider re-opening this issue - it is a more up to date description of the problem - my issue is a bit older, and so starts off describing an older issue, whereas yours describes what I believe to be the current issue - and the issues the Bitwarden team need to address:

  1. the user could not be verified
  2. failure to display the username, just the cipher
<!-- gh-comment-id:2467588168 --> @BJReplay commented on GitHub (Nov 11, 2024): @Molenaar2 I think you should consider re-opening this issue - it is a more up to date description of the problem - my issue is a bit older, and so starts off describing an older issue, whereas yours describes what I believe to be the current issue - and the issues the Bitwarden team need to address: 1. the user could not be verified 2. failure to display the username, just the cipher
GiteaMirror commented 2026-05-01 11:39:07 -05:00
Author
Owner
Copy Link

@Molenaar2 commented on GitHub (Nov 11, 2024):

Reopened as advised by @BJReplay

<!-- gh-comment-id:2467703471 --> @Molenaar2 commented on GitHub (Nov 11, 2024): Reopened as advised by @BJReplay
GiteaMirror commented 2026-05-01 11:39:08 -05:00
Author
Owner
Copy Link

@cipavlou commented on GitHub (Nov 16, 2024):

Also having this issue - cannot login with my passkey. Worked in non-native but doesn't work in native. Have just the one passkey

<!-- gh-comment-id:2480836178 --> @cipavlou commented on GitHub (Nov 16, 2024): Also having this issue - cannot login with my passkey. Worked in non-native but doesn't work in native. Have just the one passkey
GiteaMirror commented 2026-05-01 11:39:09 -05:00
Author
Owner
Copy Link

@BJReplay commented on GitHub (Nov 16, 2024):

Also have this issue. One account, one passkey. Samsung S22U A14 - works in legacy but not native.

<!-- gh-comment-id:2480842584 --> @BJReplay commented on GitHub (Nov 16, 2024): Also have this issue. One account, one passkey. Samsung S22U A14 - works in legacy but not native.
GiteaMirror commented 2026-05-01 11:39:10 -05:00
Author
Owner
Copy Link

@Tasqa commented on GitHub (Nov 24, 2024):

I also ran into this issue on Version: 2024.11.6 (19499)

Even though the Bitwarden settings said the session timeout was 15min it immediately logged out, causing this bug. Because the native passkey UV is not shown when there is not session. I reconfirmed the session timeout to 15 minutes and now the user verification does show properly and I can login.

<!-- gh-comment-id:2496080904 --> @Tasqa commented on GitHub (Nov 24, 2024): I also ran into this issue on Version: 2024.11.6 (19499) Even though the Bitwarden settings said the session timeout was 15min it immediately logged out, causing this bug. Because the native passkey UV is not shown when there is not session. I reconfirmed the session timeout to 15 minutes and now the user verification does show properly and I can login.
GiteaMirror commented 2026-05-01 11:39:11 -05:00
Author
Owner
Copy Link

@Molenaar2 commented on GitHub (Nov 24, 2024):

@Tasqa sorry, I'm not sure I understand your comment. Are you able to login to UBank via a passkey stored in Bitwarden by increasing the session timeout in the new native Bitwarden app for Android to 15 minutes? I have tried that as well and that does not make a difference. We are still not able to login to UBank.

<!-- gh-comment-id:2496279026 --> @Molenaar2 commented on GitHub (Nov 24, 2024): @Tasqa sorry, I'm not sure I understand your comment. Are you able to login to UBank via a passkey stored in Bitwarden by increasing the session timeout in the new native Bitwarden app for Android to 15 minutes? I have tried that as well and that does not make a difference. We are still not able to login to UBank.
GiteaMirror commented 2026-05-01 11:39:12 -05:00
Author
Owner
Copy Link

@lindhe commented on GitHub (Nov 27, 2024):

Can we get a better title on this issue? I skipped over it because it looked so generic, but it is in fact a specific and important bug report.

<!-- gh-comment-id:2504764087 --> @lindhe commented on GitHub (Nov 27, 2024): Can we get a better title on this issue? I skipped over it because it looked so generic, but it is in fact a specific and important bug report.
GiteaMirror commented 2026-05-01 11:39:13 -05:00
Author
Owner
Copy Link

@kmahyyg commented on GitHub (Dec 26, 2024):

Hi team,

I think #4385 shouldn't be closed, this is actually another bug should be considered as a sub-issue.

As I've met the same issue on the official client for a long time.

To have a reproducible bug report, please follow the following steps to reproduce:

Version: 2024.12.0 (19597) on Android 15
Device: OnePlus 12 running OxygenOS 15

To reproduce:

  • Set session lockout time to "immediate"
  • Go back to Chrome and make sure system auto-fill settings are configured as instructed.
  • Set bitwarden as passkeys provider and enabled auto-fill.
  • Now the vault should be locked
  • Go to GitHub.com and choose login with passkeys
  • Choose auto-fill button on keyboard and unlock as UI shown
  • Confirm Passkeys request in bitwarden
  • Then will fail and show pop-up: "user couldn't be verified"

Temporary workaround:

  • Set session timeout to ones other than "immediate" and make sure to unlock vault in app before you call it.

@cbbit

<!-- gh-comment-id:2562292391 --> @kmahyyg commented on GitHub (Dec 26, 2024): Hi team, I think #4385 shouldn't be closed, this is actually another bug should be considered as a sub-issue. As I've met the same issue on the official client for a long time. To have a reproducible bug report, please follow the following steps to reproduce: Version: 2024.12.0 (19597) on Android 15 Device: OnePlus 12 running OxygenOS 15 To reproduce: - Set session lockout time to "immediate" - Go back to Chrome and make sure system auto-fill settings are configured as instructed. - Set bitwarden as passkeys provider and enabled auto-fill. - Now the vault should be locked - Go to GitHub.com and choose login with passkeys - Choose auto-fill button on keyboard and unlock as UI shown - Confirm Passkeys request in bitwarden - Then will fail and show pop-up: "user couldn't be verified" Temporary workaround: - Set session timeout to ones other than "immediate" and make sure to unlock vault in app before you call it. @cbbit
GiteaMirror commented 2026-05-01 11:39:14 -05:00
Author
Owner
Copy Link

@kmahyyg commented on GitHub (Dec 26, 2024):

It seems also a race-condition issue looks similar like #4408 .

<!-- gh-comment-id:2562295656 --> @kmahyyg commented on GitHub (Dec 26, 2024): It seems also a race-condition issue looks similar like #4408 .
GiteaMirror commented 2026-05-01 11:39:15 -05:00
Author
Owner
Copy Link

@Molenaar2 commented on GitHub (Dec 26, 2024):

@kmahyyg just to make sure, the steps to reproduce you provide above, are related to #4385, and have nothing/not as much to do with the defect reported in this issue, as my vault is not locked at all when the system prevents me to login to UBank with a passkey. Probably good to add the steps to reproduce to #4385

<!-- gh-comment-id:2562349282 --> @Molenaar2 commented on GitHub (Dec 26, 2024): @kmahyyg just to make sure, the steps to reproduce you provide above, are related to #4385, and have nothing/not as much to do with the defect reported in this issue, as my vault is not locked at all when the system prevents me to login to UBank with a passkey. Probably good to add the steps to reproduce to #4385
GiteaMirror commented 2026-05-01 11:39:16 -05:00
Author
Owner
Copy Link

@kmahyyg commented on GitHub (Dec 26, 2024):

@kmahyyg just to make sure, the steps to reproduce you provide above, are related to #4385, and have nothing/not as much to do with the defect reported in this issue, as my vault is not locked at all when the system prevents me to login to UBank with a passkey. Probably good to add the steps to reproduce to #4385

Only gods know which issue is correct. This issue is covering a more broad topic, and both issues share the same error message.

<!-- gh-comment-id:2562352138 --> @kmahyyg commented on GitHub (Dec 26, 2024): > @kmahyyg just to make sure, the steps to reproduce you provide above, are related to #4385, and have nothing/not as much to do with the defect reported in this issue, as my vault is not locked at all when the system prevents me to login to UBank with a passkey. Probably good to add the steps to reproduce to #4385 Only gods know which issue is correct. This issue is covering a more broad topic, and both issues share the same error message.
GiteaMirror commented 2026-05-01 11:39:17 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 6, 2025):

Same issue on:

  • GrapheneOS (Android 15)
  • Samsung (OneUI 6.1 / Android 14)
<!-- gh-comment-id:2572871771 --> @ghost commented on GitHub (Jan 6, 2025): Same issue on: - GrapheneOS (Android 15) - Samsung (OneUI 6.1 / Android 14)
GiteaMirror commented 2026-05-01 11:39:17 -05:00
Author
Owner
Copy Link

@AngaBlue commented on GitHub (Jan 21, 2025):

Confirming that this is still an issue. I worked around by creating a passkey (for ubank specifically) with Google's credential manager and enabling it.

<!-- gh-comment-id:2604820284 --> @AngaBlue commented on GitHub (Jan 21, 2025): Confirming that this is still an issue. I worked around by creating a passkey (for ubank specifically) with Google's credential manager and enabling it.
GiteaMirror commented 2026-05-01 11:39:18 -05:00
Author
Owner
Copy Link

@TheWranger commented on GitHub (Feb 5, 2025):

Can no longer access my bank with all my money in it because bitwarden auto-updated and re-introduced this bug. Please fix!

<!-- gh-comment-id:2635856297 --> @TheWranger commented on GitHub (Feb 5, 2025): Can no longer access my bank with all my money in it because bitwarden auto-updated and re-introduced this bug. Please fix!
GiteaMirror commented 2026-05-01 11:39:19 -05:00
Author
Owner
Copy Link

@lexiismadd commented on GitHub (Feb 15, 2025):

I'm also experiencing this issue too.

I've noticed when the Ubank app stores the passkey, it's saved under androidapp://au.com.bank86400 and when the Ubank app prompts for password or passkey, it looks for https://bank86400 instead of the same one as the passkey.

<!-- gh-comment-id:2660588404 --> @lexiismadd commented on GitHub (Feb 15, 2025): I'm also experiencing this issue too. I've noticed when the Ubank app stores the passkey, it's saved under androidapp://au.com.bank86400 and when the Ubank app prompts for password or passkey, it looks for https://bank86400 instead of the same one as the passkey.
GiteaMirror commented 2026-05-01 11:39:20 -05:00
Author
Owner
Copy Link

@Molenaar2 commented on GitHub (Feb 15, 2025):

@lexiismadd I noticed that as well and saved both URLs in the same entry. But overall still not working because of the error reported in this thread.

<!-- gh-comment-id:2660700546 --> @Molenaar2 commented on GitHub (Feb 15, 2025): @lexiismadd I noticed that as well and saved both URLs in the same entry. But overall still not working because of the error reported in this thread.
GiteaMirror commented 2026-05-01 11:39:21 -05:00
Author
Owner
Copy Link

@lexiismadd commented on GitHub (Feb 15, 2025):

@lexiismadd I noticed that as well and saved both URLs in the same entry. But overall still not working because of the error reported in this thread.

Thanks for that info, at least I won't hound ubank developers about that discrepancy now. 😊

<!-- gh-comment-id:2660701305 --> @lexiismadd commented on GitHub (Feb 15, 2025): > [@lexiismadd](https://github.com/lexiismadd) I noticed that as well and saved both URLs in the same entry. But overall still not working because of the error reported in this thread. Thanks for that info, at least I won't hound ubank developers about that discrepancy now. 😊
GiteaMirror commented 2026-05-01 11:39:22 -05:00
Author
Owner
Copy Link

@Molenaar2 commented on GitHub (Feb 15, 2025):

Well, that point is still a strange thing on UBank side, but you can work around it by storing both URIs in the vault entry that has the passkey. I reckon UBank's implementation has some strange aspects as well.

<!-- gh-comment-id:2660702789 --> @Molenaar2 commented on GitHub (Feb 15, 2025): Well, that point is still a strange thing on UBank side, but you can work around it by storing both URIs in the vault entry that has the passkey. I reckon UBank's implementation has some strange aspects as well.
GiteaMirror commented 2026-05-01 11:39:23 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Feb 18, 2025):

Hi all,

I'm happy to say https://github.com/bitwarden/android/pull/4694 should resolve the issues with UBank. The fix will be available in our next scheduled release. If you would like to test out the fix prior to the release, feel free to install a beta or dev version of this build.

If you continue encountering issues after the update please let us know.

<!-- gh-comment-id:2666687896 --> @SaintPatrck commented on GitHub (Feb 18, 2025): Hi all, I'm happy to say https://github.com/bitwarden/android/pull/4694 should resolve the issues with UBank. The fix will be available in our next scheduled release. If you would like to test out the fix prior to the release, feel free to install a beta or dev version of [this build](https://github.com/bitwarden/android/actions/runs/13296456078). If you continue encountering issues after the update please let us know.
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 bug
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#50139
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?