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

It is impossible to specify the exact password length #2175

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

Originally created by @severgun on GitHub (Feb 18, 2025).

Steps To Reproduce

  1. Go to password generator
  2. Try to set exact number first try.
  3. Fail on that.

Expected Result

If I want 10 chars in password I should have 10.

Actual Result

8
9
11
9
11

Screenshots or Videos

No response

Additional Context

Please add +- buttons or make it editable as text

Build Version

© Bitwarden Inc. 2015-2025 Version: 2025.1.2 (19740) 📱 google Pixel 7 Pro 🤖 15@35 📦 prod local

What server are you connecting to?

N/A

Self-host Server Version

No response

Environment Details

© Bitwarden Inc. 2015-2025

Version: 2025.1.2 (19740)
📱 google Pixel 7 Pro 🤖 15@35 📦 prod
local

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 @severgun on GitHub (Feb 18, 2025). ### Steps To Reproduce 1. Go to password generator 2. Try to set exact number first try. 3. Fail on that. ### Expected Result If I want 10 chars in password I should have 10. ### Actual Result 8 9 11 9 11 ### Screenshots or Videos _No response_ ### Additional Context Please add +- buttons or make it editable as text ### Build Version © Bitwarden Inc. 2015-2025 Version: 2025.1.2 (19740) 📱 google Pixel 7 Pro 🤖 15@35 📦 prod local ### What server are you connecting to? N/A ### Self-host Server Version _No response_ ### Environment Details © Bitwarden Inc. 2015-2025 Version: 2025.1.2 (19740) 📱 google Pixel 7 Pro 🤖 15@35 📦 prod local ### 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:11:03 -06:00
GiteaMirror commented 2025-11-26 23:11:03 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 18, 2025):

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

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

@daniellbw commented on GitHub (Feb 18, 2025):

Hi there,

I attempted to reproduce your issue and was unable to do so.

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 and search to see if this request already exists (https://community.bitwarden.com/signup). 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. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum.

Thanks!

@daniellbw commented on GitHub (Feb 18, 2025): Hi there, I attempted to reproduce your issue and was unable to do so. 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 and search to see if this request already exists (https://community.bitwarden.com/signup). 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. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum. Thanks!
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#2175
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?