You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Be told: "premium subscription needed" on the view after the TOTP secret has been entered. Closing the view and reopening it clears the message and shows the TOTP key.
Screenshots or Videos
Additional Context
This is a regression in usability from previous versions.
Operating System
Windows
Operating System Version
10 22H2
Web Browser
Firefox
Browser Version
125.0.1
Build Version
2024.4.1
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.
The text was updated successfully, but these errors were encountered:
I hadn't found the exact steps that cause it to go into showing premium required, but it comes up during setup periodically especially on new account setup when giving a tour to new users. Started with last version.
You guys need to step up the QA on extension releases...OTP copy bug, now premium warning bug...every version is introducing a new problem.
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.
Steps To Reproduce
Expected Result
See the TOTP number.
Actual Result
Be told: "premium subscription needed" on the view after the TOTP secret has been entered. Closing the view and reopening it clears the message and shows the TOTP key.
Screenshots or Videos
Additional Context
This is a regression in usability from previous versions.
Operating System
Windows
Operating System Version
10 22H2
Web Browser
Firefox
Browser Version
125.0.1
Build Version
2024.4.1
Issue Tracking Info
The text was updated successfully, but these errors were encountered: