[PM-36855] Unable to change "Require master password on app restart" after "Unlock with PIN" has been set
- Dominant language
- Kotlin
- Stars
- 9.4k
- Forks
- 1.1k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 67
Description
### 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
### 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"...
... 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.
Contributor guide
Assessment
This issue has not been assessed yet.