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

[pamperer562580892423]

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: Unable to change "Require master password on browser restart" after "Unlock with PIN" has been set clients#18281
• Browser extension: Unable to set "Require master password on browser restart" if it is not set when creating a PIN clients#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 bitwarden/clients#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: 61955d7
💻 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.

[bitwarden-bot]

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

[rmcdowell-bitwarden]

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!