github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-10 04:03:24 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

No Way to Revert UI to Black #2096

New Issue
Closed
opened 2025-11-26 23:08:02 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-26 23:08:02 -06:00
Owner
Copy Link

Originally created by @ItsRogueRen on GitHub (Dec 6, 2024).

Steps To Reproduce

  1. Go to settings
  2. Click on appearance

Expected Result

An option for a black UI, not Material You

Actual Result

Only gives an option for Light more or all blue

Screenshots or Videos

No response

Additional Context

Material You looks absolutely disgusting in dark mode. A proper black is needed.

Build Version

2024.11.7

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Moto G Stylus 5G 2023, Android 14

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 @ItsRogueRen on GitHub (Dec 6, 2024). ### Steps To Reproduce 1. Go to settings 2. Click on appearance ### Expected Result An option for a black UI, not Material You ### Actual Result Only gives an option for Light more or all blue ### Screenshots or Videos _No response_ ### Additional Context Material You looks absolutely disgusting in dark mode. A proper black is needed. ### Build Version 2024.11.7 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Moto G Stylus 5G 2023, Android 14 ### 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 bug label 2025-11-26 23:08:02 -06:00
GiteaMirror commented 2025-11-26 23:08:02 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Dec 6, 2024):

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

@bitwarden-bot commented on GitHub (Dec 6, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-15636
GiteaMirror commented 2025-11-26 23:08:02 -06:00
Author
Owner
Copy Link

@cbbit commented on GitHub (Dec 6, 2024):

Hi there,

Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request.

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed.

Thanks!

@cbbit commented on GitHub (Dec 6, 2024): Hi there, Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request. We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/ Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked. This issue will now be closed. Thanks!
GiteaMirror commented 2025-11-26 23:08:03 -06:00
Author
Owner
Copy Link

@ItsRogueRen commented on GitHub (Dec 6, 2024):

Hi there,

Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request.

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed.

Thanks!

How is it not a bug that a setting that used to be there is now missing?

@ItsRogueRen commented on GitHub (Dec 6, 2024): > Hi there, > > Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request. > > We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/ > > Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked. > > This issue will now be closed. > > Thanks! How is it not a bug that a setting that used to be there is now missing?
GiteaMirror commented 2025-11-26 23:08:03 -06:00
Author
Owner
Copy Link

@NicholasFlamy commented on GitHub (Apr 4, 2025):

As this is a regression and not a feature request, I believe that this issue should be reopened.

@NicholasFlamy commented on GitHub (Apr 4, 2025): As this is a regression and not a feature request, I believe that this issue should be reopened.
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 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#2096
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?