github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 11:29:37 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #5638] [PM-24428] After setting the night mode, the status bar of the app is still white, which looks relatively incongruous #21561

New Issue
Closed
opened 2026-04-16 22:05:57 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-16 22:05:57 -05:00
Owner
Copy Link

Originally created by @DearZack on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5638

Steps To Reproduce

After setting the night mode, the status bar of the app is still white, which looks relatively incongruous

Expected Result

After setting the night mode, the status bar of the app is still white, which looks relatively incongruous

Actual Result

After setting the night mode, the status bar of the app is still white, which looks relatively incongruous

Screenshots or Videos

No response

Additional Context

No response

Build Version

2025.7.1

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

No response

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.
Originally created by @DearZack on GitHub (Aug 4, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5638 ### Steps To Reproduce After setting the night mode, the status bar of the app is still white, which looks relatively incongruous ### Expected Result After setting the night mode, the status bar of the app is still white, which looks relatively incongruous ### Actual Result After setting the night mode, the status bar of the app is still white, which looks relatively incongruous ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2025.7.1 ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details _No response_ ### Issue Tracking Info - [x] 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.
GiteaMirror added the app:password-managerbug labels 2026-04-16 22:05:57 -05:00
GiteaMirror commented 2026-04-16 22:05:59 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 4, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-24428

<!-- gh-comment-id:3149463893 --> @bitwarden-bot commented on GitHub (Aug 4, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-24428
GiteaMirror commented 2026-04-16 22:06:00 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Aug 4, 2025):

Duplicate of https://github.com/bitwarden/android/issues/5476

<!-- gh-comment-id:3149748648 --> @pamperer562580892423 commented on GitHub (Aug 4, 2025): Duplicate of https://github.com/bitwarden/android/issues/5476
GiteaMirror commented 2026-04-16 22:06:00 -05:00
Author
Owner
Copy Link

@DearZack commented on GitHub (Aug 4, 2025):

Duplicate of #5476

In fact, there should be a way to circumvent it. I am also using "Authenticator"（v2025.7.1-bwa）, and it is fine.

<!-- gh-comment-id:3149780884 --> @DearZack commented on GitHub (Aug 4, 2025): > Duplicate of [#5476](https://github.com/bitwarden/android/issues/5476) In fact, there should be a way to circumvent it. I am also using "Authenticator"（[v2025.7.1-bwa](https://github.com/bitwarden/android/releases/tag/v2025.7.1-bwa)）, and it is fine.
GiteaMirror commented 2026-04-16 22:06:01 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Aug 4, 2025):

I think there already is a fix for this issue: https://github.com/bitwarden/android/pull/5617

<!-- gh-comment-id:3149812494 --> @pamperer562580892423 commented on GitHub (Aug 4, 2025): I think there already is a fix for this issue: https://github.com/bitwarden/android/pull/5617
GiteaMirror commented 2026-04-16 22:06:01 -05:00
Author
Owner
Copy Link

@DearZack commented on GitHub (Aug 4, 2025):

I think there already is a fix for this issue: #5617

I am using a package released 3 days ago（2025.7.1）, but I still have this problem. Is this pr not yet merged into the main branch?

<!-- gh-comment-id:3149826772 --> @DearZack commented on GitHub (Aug 4, 2025): > I think there already is a fix for this issue: [#5617](https://github.com/bitwarden/android/pull/5617) I am using a package released 3 days ago（2025.7.1）, but I still have this problem. Is this pr not yet merged into the main branch?
GiteaMirror commented 2026-04-16 22:06:02 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Aug 4, 2025):

I am using a package released 3 days ago（2025.7.1）, but I still have this problem. Is this pr not yet merged into the main branch?

The fix was merged five days ago. 2025.7.0 (!) was released 10 days ago - and 2025.7.1 (!) seems to have been only a hotfix for some Android 13 crashes. So, we have to at least wait for 2025.8.x I guess.

<!-- gh-comment-id:3149926133 --> @pamperer562580892423 commented on GitHub (Aug 4, 2025): > I am using a package released 3 days ago（2025.7.1）, but I still have this problem. Is this pr not yet merged into the main branch? The fix was merged five days ago. 2025.7.0 (!) was released 10 days ago - and 2025.7.1 (!) seems to have been only a hotfix for some Android 13 crashes. So, we have to at least wait for 2025.8.x I guess.
GiteaMirror commented 2026-04-16 22:06:02 -05:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Aug 19, 2025):

The 2025.8.0 release is coming soon and will include a patch for the issues causing the system bars to be the incorrect color.
This issue is caused by an OS bug that has been resolved by Google but older versions of Android 15 still exhibit the issue. Because of the this, we have targeted specific revisions to apply our work-around and there may still be a minor blink affect on those devices when logging in or changing users.

<!-- gh-comment-id:3202004487 --> @david-livefront commented on GitHub (Aug 19, 2025): The 2025.8.0 release is coming soon and will include a patch for the issues causing the system bars to be the incorrect color. This issue is caused by an OS bug that has been resolved by Google but older versions of Android 15 still exhibit the issue. Because of the this, we have targeted specific revisions to apply our work-around and there may still be a minor blink affect on those devices when logging in or changing users.
GiteaMirror commented 2026-04-16 22:06:03 -05:00
Author
Owner
Copy Link

@DearZack commented on GitHub (Aug 22, 2025):

The 2025.8.0 release is coming soon and will include a patch for the issues causing the system bars to be the incorrect color. This issue is caused by an OS bug that has been resolved by Google but older versions of Android 15 still exhibit the issue. Because of the this, we have targeted specific revisions to apply our work-around and there may still be a minor blink affect on those devices when logging in or changing users.

I installed version 2025.8.0, and the problem has been fixed

<!-- gh-comment-id:3212607979 --> @DearZack commented on GitHub (Aug 22, 2025): > The 2025.8.0 release is coming soon and will include a patch for the issues causing the system bars to be the incorrect color. This issue is caused by an OS bug that has been resolved by Google but older versions of Android 15 still exhibit the issue. Because of the this, we have targeted specific revisions to apply our work-around and there may still be a minor blink affect on those devices when logging in or changing users. I installed version 2025.8.0, and the problem has been fixed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21561
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?