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

ipad ios 17, can not log in with yubikey, #1713

New Issue
Closed
opened 2025-11-26 22:56:05 -06:00 by GiteaMirror · 17 comments
GiteaMirror commented 2025-11-26 22:56:05 -06:00
Owner
Copy Link

Originally created by @Nephilimi on GitHub (Sep 5, 2023).

Steps To Reproduce

I've used bitwarden on ios 17 on ipad for a number of weeks now, but the 2FA challenge was originally done on ios 16. Today I tried to log into my work vault and ran into this problem below, which failed. Somehow failing to log into my work account logged me out of my personal account (is that a feature or another bug?).

Now I'm logged out of my personal account with the same problem as below. For the record my yubikey is set up as webauthn and regular yubikey on both of these accounts but I'm forced to webauthn here.

There's about three bugs in this report but the huge one is I can't get into either of my vaults.

Where are we on ios/ipados 17 support?

  1. Intially app retained my personal account email, logging in on bitwarden.com
  2. master password entry screen.
  3. FIDO2 WebAuthn challenge screen. ***** NOTE how you can't see the the blue "Authenticate WebAuthn" button on this screen, it took me a while to learn this little screen needs to be scrolled DOWN*****
  4. Then I get what appears to be a ios Sign In screen.
  5. It does not matter what option I chose here, both of them proceed to settings.app in the Password Options section. What am I to do here??
  6. If I then click the top left link back to Bitwarden I'm presented with message "Please make sure your default browser supports WebAuthn and try again".
  7. Close that error message and I'm left with a completely blank window with the bitwarden logo. ****** NOTE nothing I can do here, you are forced to close the app and swipe it out of memory to start over.

Note; I'm beta testing Vivaldi but changing default browser back to Safari and doing this over again does not change anything here, you still go to settings.

Expected Result

Successful 2FA challenge

sub issues;

  1. blue "Authenticate WebAuthn" button must be visible without scrolling.
  2. If 2FA challenge process fails put something on the screen so the user can start over without force quitting the app.

Actual Result

Settings screen opens instead of initiating 2FA challenge, which I guess requires a browser?

Screenshots or Videos

1 challenge, what do I do here?
1 challenge
2 have to scroll to see button
2 have to scroll to see button
3 chose how to sign in. Chose either one, both of them lead to the settings app??
3 chose how to sign in
4 why did settings open?
4 why did settings open
5 error occured
5 error occured
6 completely blank useless screen can't do anything. Have to force quit and start over.
6 completely blank useless screen can't do anything

Additional Context

No response

Operating System

iOS

Operating System Version

17 public beta 21A5326a

Device

ipad pro M1

Build Version

Whatever is current in app store, I can't get in to see this...

Beta

  • Using a pre-release version of the application.
Originally created by @Nephilimi on GitHub (Sep 5, 2023). ### Steps To Reproduce I've used bitwarden on ios 17 on ipad for a number of weeks now, but the 2FA challenge was originally done on ios 16. Today I tried to log into my work vault and ran into this problem below, which failed. Somehow failing to log into my work account logged me out of my personal account (is that a feature or another bug?). Now I'm logged out of my personal account with the same problem as below. For the record my yubikey is set up as webauthn and regular yubikey on both of these accounts but I'm forced to webauthn here. There's about three bugs in this report but the huge one is I can't get into either of my vaults. Where are we on ios/ipados 17 support? 1. Intially app retained my personal account email, logging in on bitwarden.com 2. master password entry screen. 3. FIDO2 WebAuthn challenge screen. ***** NOTE how you can't see the the blue "Authenticate WebAuthn" button on this screen, it took me a while to learn this little screen needs to be scrolled DOWN***** 4. Then I get what appears to be a ios Sign In screen. 5. It does not matter what option I chose here, both of them proceed to settings.app in the Password Options section. What am I to do here?? 6. If I then click the top left link back to Bitwarden I'm presented with message "Please make sure your default browser supports WebAuthn and try again". 7. Close that error message and I'm left with a completely blank window with the bitwarden logo. ****** NOTE nothing I can do here, you are forced to close the app and swipe it out of memory to start over. Note; I'm beta testing Vivaldi but changing default browser back to Safari and doing this over again does not change anything here, you still go to settings. ### Expected Result Successful 2FA challenge sub issues; 1. blue "Authenticate WebAuthn" button must be visible without scrolling. 2. If 2FA challenge process fails put _something_ on the screen so the user can start over without force quitting the app. ### Actual Result Settings screen opens instead of initiating 2FA challenge, which I guess requires a browser? ### Screenshots or Videos 1 challenge, what do I do here? ![1 challenge](https://github.com/bitwarden/mobile/assets/26043969/babe7789-8263-429a-86bc-daf5f5d056c0) 2 have to scroll to see button ![2 have to scroll to see button](https://github.com/bitwarden/mobile/assets/26043969/121b6fd9-84f2-49e3-be34-2e13f40e8ed9) 3 chose how to sign in. Chose either one, both of them lead to the settings app?? ![3 chose how to sign in](https://github.com/bitwarden/mobile/assets/26043969/bc0f6fab-3ed8-4c09-bcc8-2f0d38f5a99e) 4 why did settings open? ![4 why did settings open](https://github.com/bitwarden/mobile/assets/26043969/53be2751-12dd-410f-8943-e6da0625bbef) 5 error occured ![5 error occured](https://github.com/bitwarden/mobile/assets/26043969/5a0381db-76bb-4620-8bbd-531f50450af5) 6 completely blank useless screen can't do anything. Have to force quit and start over. ![6 completely blank useless screen can't do anything](https://github.com/bitwarden/mobile/assets/26043969/afcf109d-11ed-455b-8b61-e1b6ec835b0d) ### Additional Context _No response_ ### Operating System iOS ### Operating System Version 17 public beta 21A5326a ### Device ipad pro M1 ### Build Version Whatever is current in app store, I can't get in to see this... ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:56:05 -06:00
GiteaMirror commented 2025-11-26 22:56:06 -06:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Sep 6, 2023):

I was able to finally get back into my personal account but I can't get into my work account still. I am not able to use this workaround to get into my other account because #2 below just results in the "autofill enabled" splash screen.

  1. Above same process but when you get to the settings app uncheck Bitwarden in the "use passcodes and passkeys from" section
  2. Recheck Bitwarden in that same section. Because you have nothing logged in, it brings you back to the login process.
  3. I was again prompted for webauthn popup BUT this time there was a three dot menu item in the top right of the pop up window, tapping that lead me to "use other 2FA methods", and selecting that I was FINALLY able to use yubikey.
  4. That brought me to the youbikey prompt, and this is where I'm about to lose it because this window is asking me to do NFC which i'm reasonably certain the ipad doesn't have. BUT because THAT bug was reported (not fixed) years ago I know there is a hidden/invisible text entry window on this screen, shown in the picture below today still broken. So now I tap this invisible text entry section, plug in my USB-C yubikey and I'm able to complete authentication.

Super secret and well hidden text entry section you have to find to get this working on ipad.
Reference issues;

@Nephilimi commented on GitHub (Sep 6, 2023): I was able to finally get back into my personal account but I can't get into my work account still. I am not able to use this workaround to get into my other account because #2 below just results in the "autofill enabled" splash screen. 1. Above same process but when you get to the settings app uncheck Bitwarden in the "use passcodes and passkeys from" section 2. Recheck Bitwarden in that same section. Because you have nothing logged in, it brings you back to the login process. 3. I was again prompted for webauthn popup BUT this time there was a three dot menu item in the top right of the pop up window, tapping that lead me to "use other 2FA methods", and selecting that I was FINALLY able to use yubikey. 4. That brought me to the youbikey prompt, and this is where I'm about to lose it because this window is asking me to do NFC which i'm reasonably certain the ipad doesn't have. BUT because THAT bug was reported (not fixed) years ago I know there is a hidden/invisible text entry window on this screen, shown in the picture below today still broken. So now I tap this invisible text entry section, plug in my USB-C yubikey and I'm able to complete authentication. Super secret and well hidden text entry section you have to find to get this working on ipad. Reference issues; - https://github.com/bitwarden/mobile/issues/592 and the original issue from 2019 is - https://github.com/bitwarden/mobile/issues/679 ![IMG_0316](https://github.com/bitwarden/mobile/assets/26043969/370d1590-f9e9-4873-b41c-e58678b4d3a4)
GiteaMirror commented 2025-11-26 22:56:06 -06:00
Author
Owner
Copy Link

@kevinfengcu commented on GitHub (Sep 6, 2023):

Try inserting the key and touching the button when you see the iPadOS system prompt (i.e. step 3), ignoring both options.
This looks like an iPadOS bug/intended process change as it happens with other WebAuthn login.

@kevinfengcu commented on GitHub (Sep 6, 2023): Try inserting the key and touching the button when you see the iPadOS system prompt (i.e. step 3), ignoring both options. This looks like an iPadOS bug/intended process change as it happens with other WebAuthn login.
GiteaMirror commented 2025-11-26 22:56:07 -06:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Sep 6, 2023):

Try inserting the key and touching the button when you see the iPadOS system prompt (i.e. step 3), ignoring both options. This looks like an iPadOS bug/intended process change as it happens with other WebAuthn login.

Thank You, that was the answer! I never would have figured that out just fumbling around and following directions.

So this is really a bug under iOS 17 I should be reporting to Apple? Bitwarden has no control over that dialog right?

What about not being able to select an alternate 2FA method like I was able to do in my workaround?

It certainly appears that bitwarden app has control of the blue authenticate button not being visible, file as separate bug?

@Nephilimi commented on GitHub (Sep 6, 2023): > Try inserting the key and touching the button when you see the iPadOS system prompt (i.e. step 3), ignoring both options. This looks like an iPadOS bug/intended process change as it happens with other WebAuthn login. Thank You, that was the answer! I never would have figured that out just fumbling around and following directions. So this is really a bug under iOS 17 I should be reporting to Apple? Bitwarden has no control over that dialog right? What about not being able to select an alternate 2FA method like I was able to do in my workaround? It certainly appears that bitwarden app has control of the blue authenticate button not being visible, file as separate bug?
GiteaMirror commented 2025-11-26 22:56:07 -06:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Sep 6, 2023):

iOS beta feedback filed. FB13129207 (Webauthn challenge does not tell user to use security key now, leads to security settings.)

@Nephilimi commented on GitHub (Sep 6, 2023): iOS beta feedback filed. FB13129207 (Webauthn challenge does not tell user to use security key now, leads to security settings.)
GiteaMirror commented 2025-11-26 22:56:08 -06:00
Author
Owner
Copy Link

@Greenderella commented on GitHub (Sep 19, 2023):

Hi there,

I have escalated this report for further investigation. If you have more information that can help us, please add it below.

Thanks!

@Greenderella commented on GitHub (Sep 19, 2023): Hi there, I have escalated this report for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2025-11-26 22:56:08 -06:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Sep 19, 2023):

Hi there,

I have escalated this report for further investigation. If you have more information that can help us, please add it below.

Thanks!

Thank you. To clarify we have four things I think need to be addressed here.

  • screenshot 1; shrink picture so Authenticate WebAuthn button is visible in system dialog box
  • screenshot 2; Is it possible to ask for / trigger alternate methods here, like yubikey?
  • Screenshot 3; I don't know what you can do about the system dialog shown here. I filed a beta bug report to apple but your group could probably get more attention than I can.
  • Follow up post screenshot; Change instructions to include what to do for devices that do not have NFC, and figure out some way to call out the text entry field so you can use yubikey. Multiple referenced issues linked in that post on this item.
@Nephilimi commented on GitHub (Sep 19, 2023): > Hi there, > > I have escalated this report for further investigation. If you have more information that can help us, please add it below. > > Thanks! Thank you. To clarify we have **four** things I think need to be addressed here. - screenshot 1; shrink picture so Authenticate WebAuthn button is visible in system dialog box - screenshot 2; Is it possible to ask for / trigger alternate methods here, like yubikey? - Screenshot 3; I don't know what you can do about the system dialog shown here. I filed a beta bug report to apple but your group could probably get more attention than I can. - Follow up post screenshot; Change instructions to include what to do for devices that do not have NFC, and figure out some way to call out the text entry field so you can use yubikey. Multiple referenced issues linked in that post on this item.
GiteaMirror commented 2025-11-26 22:56:08 -06:00
Author
Owner
Copy Link

@allddd commented on GitHub (Sep 23, 2023):

I'm having the same problem on an iPhone 14 Pro (iOS 17.0.1) using 2023.9.1.
Since I can't plug in my key and have to use NFC instead, the workaround is to place the key on the back of the phone when the iOS prompt appears, without pressing anything on the screen.
The prompt then disappears and authentication is successful.

@allddd commented on GitHub (Sep 23, 2023): I'm having the same problem on an iPhone 14 Pro (iOS 17.0.1) using 2023.9.1. Since I can't plug in my key and have to use NFC instead, the workaround is to place the key on the back of the phone when [the iOS prompt](https://user-images.githubusercontent.com/26043969/265842530-bc0f6fab-3ed8-4c09-bcc8-2f0d38f5a99e.jpeg) appears, without pressing anything on the screen. The prompt then disappears and authentication is successful.
GiteaMirror commented 2025-11-26 22:56:08 -06:00
Author
Owner
Copy Link

@ayancey commented on GitHub (Oct 6, 2023):

This is really frustrating. It affects other products that use webauthn as well.

@ayancey commented on GitHub (Oct 6, 2023): This is really frustrating. It affects other products that use webauthn as well.
GiteaMirror commented 2025-11-26 22:56:08 -06:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Oct 6, 2023):

This is really frustrating. It affects other products that use webauthn as well.

It does. All I can suggest is to temporarily turn on public beta in settings, that gets you access to the feedback app. Do a little writeup in feedback and submit it. Then you may turn off public beta so as to not actually upgrade to the beta. I've also sent this to apple on twitter, no response. There's also a feedback page for apple somewhere I haven't done yet.

@Nephilimi commented on GitHub (Oct 6, 2023): > This is really frustrating. It affects other products that use webauthn as well. It does. All I can suggest is to temporarily turn on public beta in settings, that gets you access to the feedback app. Do a little writeup in feedback and submit it. Then you may turn off public beta so as to not actually upgrade to the beta. I've also sent this to apple on twitter, no response. There's also a feedback page for apple somewhere I haven't done yet.
GiteaMirror commented 2025-11-26 22:56:08 -06:00
Author
Owner
Copy Link

@ayancey commented on GitHub (Oct 6, 2023):

This is really frustrating. It affects other products that use webauthn as well.

It does. All I can suggest is to temporarily turn on public beta in settings, that gets you access to the feedback app. Do a little writeup in feedback and submit it. Then you may turn off public beta so as to not actually upgrade to the beta. I've also sent this to apple on twitter, no response. There's also a feedback page for apple somewhere I haven't done yet.

I am not on any beta. I am on iOS 17.0.3.

@ayancey commented on GitHub (Oct 6, 2023): > > This is really frustrating. It affects other products that use webauthn as well. > > It does. All I can suggest is to temporarily turn on public beta in settings, that gets you access to the feedback app. Do a little writeup in feedback and submit it. Then you may turn off public beta so as to not actually upgrade to the beta. I've also sent this to apple on twitter, no response. There's also a feedback page for apple somewhere I haven't done yet. I am not on any beta. I am on iOS 17.0.3.
GiteaMirror commented 2025-11-26 22:56:08 -06:00
Author
Owner
Copy Link

@lucianken commented on GitHub (Nov 5, 2023):

thanks god this thread solved my issue in a different product/flow using yubikey. This is apple fault, I confirm the workaround works:

PLace the yubikey behind the phone when the Ios prompt appears without touching anything.

@lucianken commented on GitHub (Nov 5, 2023): thanks god this thread solved my issue in a different product/flow using yubikey. This is apple fault, I confirm the workaround works: PLace the yubikey behind the phone when the Ios prompt appears without touching anything.
GiteaMirror commented 2025-11-26 22:56:09 -06:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Nov 5, 2023):

If this page helped you please let apple know about it; https://www.apple.com/feedback/iphone/

@Nephilimi commented on GitHub (Nov 5, 2023): If this page helped you please let apple know about it; https://www.apple.com/feedback/iphone/
GiteaMirror commented 2025-11-26 22:56:09 -06:00
Author
Owner
Copy Link

@ajaxbits commented on GitHub (Nov 9, 2023):

Issue persists. The below did not fix for me:

PLace the yubikey behind the phone when the Ios prompt appears without touching anything.

@ajaxbits commented on GitHub (Nov 9, 2023): Issue persists. The below did not fix for me: > PLace the yubikey behind the phone when the Ios prompt appears without touching anything.
GiteaMirror commented 2025-11-26 22:56:09 -06:00
Author
Owner
Copy Link

@luuqh commented on GitHub (Nov 10, 2023):

Issue persists. The below did not fix for me:

PLace the yubikey behind the phone when the Ios prompt appears without touching anything.

Same here with my iPhone 12P + iOS17 (all versions including 17.1.1) and Yubikey 5 (USB-C and USB-A) :(

@luuqh commented on GitHub (Nov 10, 2023): > Issue persists. The below did not fix for me: > > > PLace the yubikey behind the phone when the Ios prompt appears without touching anything. Same here with my iPhone 12P + iOS17 (all versions including 17.1.1) and Yubikey 5 (USB-C and USB-A) :(
GiteaMirror commented 2025-11-26 22:56:09 -06:00
Author
Owner
Copy Link

@Nephilimi commented on GitHub (Nov 10, 2023):

In response to the recent posts this doesn't work; I just logged out of both of my devices and was able to get back in with WebAuthm on both no issues. You still need to hit the big blue Authenticate with WebAuthn button. The prompt after that one is the one you ignore. This of course assumes that you have your Bitwarden account set up to use WebAuthn 2FA in the first place.

Bitwarden on ipad via WebAuthn via USB on iOS beta 17.2, still works fine.
Bitwarden on iphone via WebAuthn via NFC on iOS 17.1.1, still works fine.

If you have Bitwarden 2FA set up to use Yubikey specifically, that is a slightly different procedure using the hidden text entry field. I believe the problem there is getting ios to switch over to alternate methods.

@Nephilimi commented on GitHub (Nov 10, 2023): In response to the recent posts this doesn't work; I just logged out of both of my devices and was able to get back in with WebAuthm on both no issues. You still need to hit the big blue Authenticate with WebAuthn button. The prompt after that one is the one you ignore. This of course assumes that you have your Bitwarden account set up to use WebAuthn 2FA in the first place. Bitwarden on ipad via WebAuthn via USB on iOS beta 17.2, still works fine. Bitwarden on iphone via WebAuthn via NFC on iOS 17.1.1, still works fine. If you have Bitwarden 2FA set up to use Yubikey specifically, that is a slightly different procedure using the hidden text entry field. I believe the problem there is getting ios to switch over to alternate methods.
GiteaMirror commented 2025-11-26 22:56:10 -06:00
Author
Owner
Copy Link

@ajaxbits commented on GitHub (Nov 10, 2023):

Sorry, should have specified @Nephilimi.

I am using WebAuthn via NFC.

However, after an uninstall-reinstall, this strategy seems to work:

PLace the yubikey behind the phone when the Ios prompt appears without touching anything.

@ajaxbits commented on GitHub (Nov 10, 2023): Sorry, should have specified @Nephilimi. I _am_ using WebAuthn via NFC. However, after an uninstall-reinstall, this strategy seems to work: > PLace the yubikey behind the phone when the Ios prompt appears without touching anything.
GiteaMirror commented 2025-11-26 22:56:10 -06:00
Author
Owner
Copy Link

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

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

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