github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-10 00:28:29 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[GH-ISSUE #6469] [PM-31634] Cannot add passkey from ubank Android App to Bitwarden #102510

New Issue
Closed
opened 2026-06-03 02:26:14 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-06-03 02:26:14 -05:00
Owner
Copy Link

Originally created by @lyneca on GitHub (Feb 2, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6469

Origin

Native Application (non-browser app)

Web URL or App name

au.com.bank86400 (https://www.ubank.com.au/)

Passkey Action

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

Build Information

© Bitwarden Inc. 2015-2026

Version: 2026.1.0 (21141)
📱 samsung SM-S936B 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2026.1-rc42@67f83e3020b53f8d41e63a7d8f6bdb759ccb9ddc
💻 build source: bitwarden/android/actions/runs/21299199924/attempts/1
🦀 SDK: 2.0.0-4441-c5a3b833
🌩 Server: 2026.1.0 @ US

Additional Information

  1. Click "Add Passkey" in app
  2. Scan fingerprint on Bitwarden popup ("Create passkey to sign into ubank?")
  3. Choose ubank entry from bitwarden app - this is only there as I have manually added au.com.bank86400 to my ubank entry's autofill list
  4. "An error has occurred" toast from Bitwarden, "Oops! Something seems to have gone wrong" from ubank.

I'm not sure whether the version I'm on is the beta or not, as I signed up to the beta and reinstalled it to attempt to fix this issue.

I was able to create a passkey via Google Password Manager with no issues, so it seems like it's something about Bitwarden specifically. I've also noticed that there is a previous issue with ubank; and I've tried the steps in that issue - setting vault timeout to 15 mins and pre-logging in - to no avail.

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 @lyneca on GitHub (Feb 2, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6469 ### Origin Native Application (non-browser app) ### Web URL or App name au.com.bank86400 (https://www.ubank.com.au/) ### Passkey Action - [x] Creating new passkey (Registration) - [ ] Signing in (Authentication) ### Build Information © Bitwarden Inc. 2015-2026 Version: 2026.1.0 (21141) 📱 samsung SM-S936B 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2026.1-rc42@67f83e3020b53f8d41e63a7d8f6bdb759ccb9ddc 💻 build source: bitwarden/android/actions/runs/21299199924/attempts/1 🦀 SDK: 2.0.0-4441-c5a3b833 🌩 Server: 2026.1.0 @ US ### Additional Information 1. Click "Add Passkey" in app 2. Scan fingerprint on Bitwarden popup ("Create passkey to sign into ubank?") 3. Choose ubank entry from bitwarden app - this is only there as I have manually added `au.com.bank86400` to my ubank entry's autofill list 4. "An error has occurred" toast from Bitwarden, "Oops! Something seems to have gone wrong" from ubank. I'm not sure whether the version I'm on is the beta or not, as I signed up to the beta and reinstalled it to attempt to fix this issue. I was able to create a passkey via Google Password Manager with no issues, so it seems like it's something about Bitwarden specifically. I've also noticed that there is a [previous issue](github.com/bitwarden/android/issues/4239) with ubank; and I've tried the steps in that issue - setting vault timeout to 15 mins and pre-logging in - to no avail. ### 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-03 02:26:14 -05:00
GiteaMirror commented 2026-06-03 02:26:17 -05:00
Author
Owner
Copy Link

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

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

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

@rmcdowell-bitwarden commented on GitHub (Feb 3, 2026):

Hi there!

Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/6454

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.

This issue will now be closed.

Thanks!

<!-- gh-comment-id:3837994599 --> @rmcdowell-bitwarden commented on GitHub (Feb 3, 2026): Hi there! Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/6454 If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. This issue will now be closed. Thanks!
GiteaMirror commented 2026-06-03 02:26:18 -05:00
Author
Owner
Copy Link

@lyneca commented on GitHub (Feb 3, 2026):

Thank you!

<!-- gh-comment-id:3838150293 --> @lyneca commented on GitHub (Feb 3, 2026): Thank you!
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#102510
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?