mobile
mobile copied to clipboard
bitwarden
[Bug] TOTP screen is closed when switching to the OTP app while logging in to Bitwarden in Safari
Steps To Reproduce
- Log in to Bitwarden on iOS
- Set the "Vault timeout" to a small number, like 15 minutes, and the "Vault timeout action" to "Log out"
- Log in to Bitwarden in Safari
- (Optional) Completely close Safari from the App Switcher
- Wait for the timeout to expire
- Open Safari and navigate to a website where you have an entry for (I did this in the Private Browsing mode)
- Click on "Passwords" to open Bitwarden
- Fill in the username and password fields
- When you see the TOTP screen, use the App Switcher to minimize Safari
- Open your OTP app and copy the TOTP
- Go back to Safari from the App Switcher
- Observe the Bitwarden login window is completely closed
- Click on "Passwords" again
- 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)
After coming back to Safari to enter the TOTP
Additional Context
No response
Operating System
iOS
Operating System Version
16.4.1
Device
iPhone XS
Build Version
2023.3.2
Beta
- [ ] Using a pre-release version of the application.
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!
@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?
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!
@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?
