github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-14 14:16:23 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

One-time key from YubiKey NFC not written to input during 2FA from iPhone AutoFill Passwords #1499

New Issue
Closed
opened 2025-11-26 22:50:47 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-26 22:50:47 -06:00
Owner
Copy Link

Originally created by @mtcarbon on GitHub (Sep 20, 2022).

Steps To Reproduce

  1. Go to a mobile app with 2FA
  2. Tap on Password field
  3. Tap on Password button
  4. Log in to Bitwarden after redirect
  5. Scan YubiKey

Expected Result

Generate one-time key, and Continue option to turn opaque.

Actual Result

iPhone notification "Firefox NFC Tag: Open in Firefox" appears.

Screenshots or Videos

The keyboard and Passwords button are not captured by the screenshot tool.
97FDFB01-444F-4732-8659-1050E0DE34E1_1_201_a
18960183-FD66-4386-948D-CF1CAA487361_1_201_a
4D7DED4E-1EDE-4E12-AFB4-7967800BE8EC_1_102_o
20615408-88F4-4F20-9AB6-352A71FD0A70_1_102_o

Additional Context

No response

Operating System

iOS

Operating System Version

15.6.1

Device

iPhone SE

Build Version

19G82

Beta

  • Using a pre-release version of the application.
Originally created by @mtcarbon on GitHub (Sep 20, 2022). ### Steps To Reproduce 1. Go to a mobile app with 2FA 2. Tap on Password field 3. Tap on Password button 4. Log in to Bitwarden after redirect 5. Scan YubiKey ### Expected Result Generate one-time key, and Continue option to turn opaque. ### Actual Result iPhone notification "Firefox NFC Tag: Open in Firefox" appears. ### Screenshots or Videos The keyboard and Passwords button are not captured by the screenshot tool. ![97FDFB01-444F-4732-8659-1050E0DE34E1_1_201_a](https://user-images.githubusercontent.com/58127651/191149654-01df626f-8a68-4bd2-9d37-775904afa2b8.jpeg) ![18960183-FD66-4386-948D-CF1CAA487361_1_201_a](https://user-images.githubusercontent.com/58127651/191149676-a102581d-e01a-4c68-8c58-594427817e7e.jpeg) ![4D7DED4E-1EDE-4E12-AFB4-7967800BE8EC_1_102_o](https://user-images.githubusercontent.com/58127651/191149699-9fbfbeb7-c8f3-41b1-9d4b-3cf9b54b796a.jpeg) ![20615408-88F4-4F20-9AB6-352A71FD0A70_1_102_o](https://user-images.githubusercontent.com/58127651/191149713-86f78832-2aa0-49c2-bdb0-efe24d2760de.jpeg) ### Additional Context _No response_ ### Operating System iOS ### Operating System Version 15.6.1 ### Device iPhone SE ### Build Version 19G82 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:50:47 -06:00
GiteaMirror commented 2025-11-26 22:50:48 -06:00
Author
Owner
Copy Link

@THEOCKID commented on GitHub (Sep 24, 2022):

ha, that same exact totally annoying popup happens to me too: iOS 16.0.2, iPhone 14 Pro (but also happened on iOS 15 with iPhone 13 mini as well): I try using the yubikey NFC and i get the pop up redirecting me to a webpage (on Opera) and it does nothing for me : I get a validation option or an option to copy the 30+ character code, but I can't get into the place I want to get in to. :(

@THEOCKID commented on GitHub (Sep 24, 2022): ha, that same exact totally annoying popup happens to me too: iOS 16.0.2, iPhone 14 Pro (but also happened on iOS 15 with iPhone 13 mini as well): I try using the yubikey NFC and i get the pop up redirecting me to a webpage (on Opera) and it does nothing for me : I get a validation option or an option to copy the 30+ character code, but I can't get into the place I want to get in to. :(
GiteaMirror commented 2025-11-26 22:50:48 -06:00
Author
Owner
Copy Link

@creyhani commented on GitHub (Oct 5, 2022):

Hello! I hope you're well!

I was able to confirm this bug and we are going to work on it ASAP. For now, the recommended work-around is to log into the Bitwarden app before you attempt to auto-fill, and setting your Vault Timeout Action to Lock instead of Logout would prevent the need for the hardware key to unlock each time.

Thanks for catching this and reporting it!

@creyhani commented on GitHub (Oct 5, 2022): Hello! I hope you're well! I was able to confirm this bug and we are going to work on it ASAP. For now, the recommended work-around is to log into the Bitwarden app before you attempt to auto-fill, and setting your Vault Timeout Action to Lock instead of Logout would prevent the need for the hardware key to unlock each time. Thanks for catching this and reporting it!
GiteaMirror commented 2025-11-26 22:50:49 -06:00
Author
Owner
Copy Link

@mpbw2 commented on GitHub (Oct 7, 2022):

@mtcarbon Thanks for the screenshots! Can you and @THEOCKID try tapping on the text entry (dark line directly above the Remember Me switch) to confirm the entry has focus before scanning your key? (This is supposed to happen automatically when that screen is first displayed but it doesn't look focused in the screenshot, which could be a bug on our part)

@mpbw2 commented on GitHub (Oct 7, 2022): @mtcarbon Thanks for the screenshots! Can you and @THEOCKID try tapping on the text entry (dark line directly above the `Remember Me` switch) to confirm the entry has focus _before_ scanning your key? (This is supposed to happen automatically when that screen is first displayed but it doesn't look focused in the screenshot, which could be a bug on our part)
GiteaMirror commented 2025-11-26 22:50:49 -06:00
Author
Owner
Copy Link

@mtcarbon commented on GitHub (Oct 8, 2022):

@mp-bw Thanks for responding. I confirmed the entry had focus (was automatic, like you said it should be) and then got the same behavior.

@mtcarbon commented on GitHub (Oct 8, 2022): @mp-bw Thanks for responding. I confirmed the entry had focus (was automatic, like you said it should be) and then got the same behavior.
GiteaMirror commented 2025-11-26 22:50:49 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/2085

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/2085
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#1499
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?