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
The status bar should display normally without visual artifacts or black bar.
Actual Result
UI artifacts appear on the status bar and sometimes black bar appears instead of UI artifacts
Screenshots or Videos
Additional Context
This issue occurs consistently in the mentioned view and could be related to rendering or UI scaling issues.
Also, I couldn't reproduce this in any other apps that I am using.
Build Version
2024.11.6
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
Device: Nothing Phone 2
OS - Android 15 (Nothing OS 3 Open Beta 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:
This issue does not occur in older versions of the Bitwarden Android app. I tested the app using an earlier version (2024.11.1) and the artifact in the status bar was not present. This suggests that the problem may have been introduced in a recent update.
Steps To Reproduce
Expected Result
The status bar should display normally without visual artifacts or black bar.
Actual Result
UI artifacts appear on the status bar and sometimes black bar appears instead of UI artifacts
Screenshots or Videos
Additional Context
This issue occurs consistently in the mentioned view and could be related to rendering or UI scaling issues.
Also, I couldn't reproduce this in any other apps that I am using.
Build Version
2024.11.6
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
Device: Nothing Phone 2
OS - Android 15 (Nothing OS 3 Open Beta 1)
Issue Tracking Info
The text was updated successfully, but these errors were encountered: