Logged in as [email protected] on __$2__.

[ejain]

Steps To Reproduce

After upgrading to 2023.12.0, the sign-in screen shows "Logged in as [email protected] on $2" instead of "Logged in as [email protected] on bitwarden.com."

Expected Result

"Logged in as [email protected] on bitwarden.com."

Actual Result

"Logged in as [email protected] on $2."

Screenshots or Videos

No response

Additional Context

Signing out and re-registering the account with master password + 2FA code resolves the issue. Simply restarting the app or the system isn't sufficient.

Operating System

Windows

Operating System Version

No response

Installation method

Direct Download (from bitwarden.com)

Build Version

2023.12.0

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.

[sammbw]

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!

[es-socrates]

Hi guys, I was going to report the same bug. I share a screenshot.

[actualwitch]

looking at the sources, the templates aren't even typechecked. the issue is here and in any sane templating setup, not passing all required props would yield a type error, but apparently not here

[Morse6690]

Had this same issue on win11.
Logging out and logging back in fixed this for me.

[erdh]

The issue started appearing again for self-hosted accounts with macOS app installed from App Store version 2024.2.0. Here is how to reproduce it on my case that might give some info why that is happening. Firstly this is a MacBook Air M1 with macOS Sonoma 14.3

• Start freshly installed Bitwarden (or start with its application data completely removed)
• Login to your Bitwarden Cloud account you have
• Configure Unlock with TouchID, Allow Browser Integration and set Vault timeout to another value, 5 minutes for example
• Lock your vault with lock combination cmd+L
• Log in to your Self-Hosted instance
• Again as you did on the Bitwarden Cloud, only configure/make sure they are configured for these 3 settings above
• Lock your Self-Hosted vault
• Get back to your Cloud account
• Unlock and lock your Cloud account
• Now switch back to your Self-Hosted vault
  __$2__ is now visible

As I searched Bitwarden Client's storage I noticed that on data.json before you switch back to your Self-Hosted vault, base value is set correctly for Self-Hosted vaults entry. At the moment you switch to Self-Hosted, base value changes to null. Manually editing value won't make a difference since Bitwarden will revert it as soon as you again switch back to Self-Hosted vault.

Edit: I just realized that I looked for something really unrelated, the unrelated info is now removed.

While recreating this bug for the 3rd time, I now encountered something a little different. Server URL is visible for self-hosted entry on data.json but __$2__ is still visible Bitwarden Application shows server url on account switcher only when Bitwarden Cloud vault is selected. Here on the first picture you can see that second entry, which is Self-Hosted vault's URL, is visible. On second picture, Self-Hosted URL is not visible when Self-Hosted account is selected.

Hope this helps debugging the issue...

[antonvh]

Same here. What is the workaround until this is fixed?