bitwarden / mobile

Retired Bitwarden mobile app for iOS and Android (MAUI/Xamarin).
https://bitwarden.com
GNU General Public License v3.0
88 stars 11 forks source link

[Bug] TOTP screen is closed when switching to the OTP app while logging in to Bitwarden in Safari #2479

Open vYq4dKP8HLiNdcorwJw29t8ryUWA6jKXUd50KKd opened 1 year ago

vYq4dKP8HLiNdcorwJw29t8ryUWA6jKXUd50KKd commented 1 year ago

Steps To Reproduce

  1. Log in to Bitwarden on iOS
  2. Set the "Vault timeout" to a small number, like 15 minutes, and the "Vault timeout action" to "Log out"
  3. Log in to Bitwarden in Safari
  4. (Optional) Completely close Safari from the App Switcher
  5. Wait for the timeout to expire
  6. Open Safari and navigate to a website where you have an entry for (I did this in the Private Browsing mode)
  7. Click on "Passwords" to open Bitwarden
  8. Fill in the username and password fields
  9. When you see the TOTP screen, use the App Switcher to minimize Safari
  10. Open your OTP app and copy the TOTP
  11. Go back to Safari from the App Switcher
  12. Observe the Bitwarden login window is completely closed
  13. Click on "Passwords" again
  14. You will go back to step 8.

Expected Result

The TOTP screen is expected to remain open when switching to the OTP app to copy a TOTP

Actual Result

The user gets somewhat stuck in an infinite loop where they can not log in to Bitwarden unless they jump through a few hoops

Screenshots or Videos

The password screen (which is followed by the TOTP screen) IMG_3756

After coming back to Safari to enter the TOTP IMG_3757

Additional Context

No response

Operating System

iOS

Operating System Version

16.4.1

Device

iPhone XS

Build Version

2023.3.2

Beta

Krychaz commented 1 year ago

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

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

Thanks once again!

vYq4dKP8HLiNdcorwJw29t8ryUWA6jKXUd50KKd commented 10 months ago

@Krychaz, this bug hasn't been resolved although 7 months have passed since the initial bug report. Can you please remind your engineering team of this annoying problem?