github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-09 16:21:19 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[GH-ISSUE #6883] [PM-36855] Unable to change "Require master password on app restart" after "Unlock with PIN" has been set #116272

New Issue
Open
opened 2026-06-09 10:03:32 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-06-09 10:03:32 -05:00
Owner
Copy Link

Originally created by @pamperer562580892423 on GitHub (May 7, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6883

Steps To Reproduce

  1. Go to 'Settings' --> 'Account Security'
  2. If an Unlock-PIN is already set, then there are no other "Steps to Reproduce"... If an Unlock-PIN is not set yet, let's continue doing this:
  3. Enable "Unlock with PIN code"
  4. Enter a PIN and "submit" it
  5. In the next dialog, you get asked "Require master password on app restart?"
  6. Either choose "No" or "Yes".

Expected Result

I should be able to change the "Require master password on browser restart" setting after "Unlock with PIN" has been set.

Actual Result

I'm not able to change the "Require master password on browser restart" setting after "Unlock with PIN" has been set.

To change that setting, you I must disable "Unlock with PIN" and then enable it again.

Screenshots or Videos

Image

 

Image

 

Image

Additional Context

This was already acknowledged as a bug for the desktop app and the browser extension - here the corresponding issues:

The browser extension does show that additional option after you set up "Unlock with PIN"...

Image

 

... but I just checked the behaviour (with extension version 2026.3.0) and it is still the same issue/bug as discussed in https://github.com/bitwarden/clients/issues/18257 - you can disable "Require master password..." afterwards, but you can't enable it afterwards.

As the Android app has the same issue, as I just realized, I thought I report it too so that it can be tracked down here as well. - BTW, please check the iOS app for this behaviour as well.

Build Version

2026.4.0 (21434)

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

© Bitwarden Inc. 2015-2026

Version: 2026.4.0 (21434)
📱 Fairphone FP5 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2026.4-rc50@61955d7cbe1546a4c467284b4a5491d4f0e47afa
💻 build source: bitwarden/android/actions/runs/23952219208/attempts/1
🦀 SDK: 2.0.0-5676-14521973
🌩 Server: 2026.4.1 @ EU

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 @pamperer562580892423 on GitHub (May 7, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6883 ### Steps To Reproduce 1. Go to 'Settings' --> 'Account Security' 2. If an Unlock-PIN is already set, then there are no other "Steps to Reproduce"... If an Unlock-PIN is not set yet, let's continue doing this: 3. Enable "Unlock with PIN code" 4. Enter a PIN and "submit" it 5. In the next dialog, you get asked "Require master password on app restart?" 6. Either choose "No" or "Yes". ### Expected Result I should be able to change the "Require master password on browser restart" setting **after** "Unlock with PIN" has been set. ### Actual Result I'm not able to change the "Require master password on browser restart" setting **after** "Unlock with PIN" has been set. To change that setting, you I must disable "Unlock with PIN" and then enable it again. ### Screenshots or Videos <img width="435" height="417" alt="Image" src="https://github.com/user-attachments/assets/4ec6bf40-c2cd-467d-89a3-1fa095a777c8" /> &nbsp; <img width="446" height="307" alt="Image" src="https://github.com/user-attachments/assets/50eb4514-2e2f-4c7e-acde-8606b2777b29" /> &nbsp; <img width="500" height="555" alt="Image" src="https://github.com/user-attachments/assets/3ac8aeb5-8ed6-4560-b5fe-c25e60a61acf" /> ### Additional Context This was already acknowledged as a bug for the desktop app and the browser extension - here the corresponding issues: - Desktop app: https://github.com/bitwarden/clients/issues/18281 - Browser extension: https://github.com/bitwarden/clients/issues/18257 The **browser extension** does show that additional option after you set up "Unlock with PIN"... <img width="603" height="321" alt="Image" src="https://github.com/user-attachments/assets/801d7657-75e3-4c29-86ef-41351159226b" /> &nbsp; ... but I just checked the behaviour (with extension version 2026.3.0) and it is still the same issue/bug as discussed in https://github.com/bitwarden/clients/issues/18257 - you can disable "Require master password..." afterwards, but you can't enable it afterwards. As the Android app has the same issue, as I just realized, I thought I report it too so that it can be tracked down here as well. - BTW, please check the iOS app for this behaviour as well. ### Build Version 2026.4.0 (21434) ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details © Bitwarden Inc. 2015-2026 Version: 2026.4.0 (21434) 📱 Fairphone FP5 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2026.4-rc50@61955d7cbe1546a4c467284b4a5491d4f0e47afa 💻 build source: bitwarden/android/actions/runs/23952219208/attempts/1 🦀 SDK: 2.0.0-5676-14521973 🌩 Server: 2026.4.1 @ EU ### 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 bugapp:password-manager labels 2026-06-09 10:03:32 -05:00
GiteaMirror commented 2026-06-09 10:03:33 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (May 7, 2026):

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

<!-- gh-comment-id:4401030183 --> @bitwarden-bot commented on GitHub (May 7, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-36855](https://bitwarden.atlassian.net/browse/PM-36855) [PM-36855]: https://bitwarden.atlassian.net/browse/PM-36855?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-06-09 10:03:33 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (May 8, 2026):

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!

<!-- gh-comment-id:4402779459 --> @rmcdowell-bitwarden commented on GitHub (May 8, 2026): 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!
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#116272
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?