Vault timeout option not respected on iOS

[3JRok3qBTRjKvEhxtgv3R0E9sDwYkY1t1mF5Ai1]

Steps To Reproduce

• Set "Vault timeout" to "Never".
• Quit Bitwarden from the App Switcher.
• Visit site and log in.
• Get prompted for master password.

Expected Result

Bitwarden would respect the Vault Timeout setting.

Actual Result

Bitwarden ignores Vault Timeout and prompts for master password for all interactions.

Screenshots or Videos

No response

Additional Context

No response

Operating System

iOS

Operating System Version

16.6.1

Device

iPhone SE 2020

Build Version

2023.9.1

Beta

• [ ] Using a pre-release version of the application.

[RX5ulL6nKunJz88UkudvsdCkM5jkiNQA74LKKeP]

Have this issue since 2023.9 update was released. Unfortunately I don’t have a way to roll back since their beta testing group is closed

[3wUV96QSheq1w3R7so2aJD96BXUQQY2pLDcPIUx]

Having the same issue on iOS 17.0.1 on my iPhone 11 Pro Max The vault always locks on app restart regardless of vault timeout or faceid settings. Definitely caused by 2023.9.0, and 2023.9.1 did not fix the issue, nor did a full re-install.

[tAbIkUi4blEAu4VW0M5YzJirfSmb81ikaEnVLxy]

Hello @ryanpcmcquen and everyone else,

Thank you for your report. I am able to reproduce this on iOS 17 with Bitwarden 2023.9.1, and I have flagged it 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.

*Edit: This also affects Bitwarden 2023.9.1 on Android 12.

Thank you again,

[RX5ulL6nKunJz88UkudvsdCkM5jkiNQA74LKKeP]

Thank you for response. Any chance of a way that we can roll back some how? I have a 20 character password which is random generated, this is nearly impossible to deal with on a routine basis.

[tAbIkUi4blEAu4VW0M5YzJirfSmb81ikaEnVLxy]

Hi @Gerardv514,

Thank you for response.

You're most welcome! 😊

Any chance of a way that we can roll back some how? I have a 20 character password which is random generated, this is nearly impossible to deal with on a routine basis.

Rolling back on iOS is not a practical option; I would recommend you set up a PIN (https://bitwarden.com/help/unlock-with-pin/) or Biometrics (https://bitwarden.com/help/biometrics/) for now if possible, as a temporary workaround.

All the best,

[RX5ulL6nKunJz88UkudvsdCkM5jkiNQA74LKKeP]

Ah Yes I can set biometric Face ID in mean time. I’m also hit with another bug of kdf memory error when not using biometric. I know a new thread should be created, but I’m not well rehearsed in the argon2 stuff hoping to see someone else post about it.

Thank you tho for biometric option

[tAbIkUi4blEAu4VW0M5YzJirfSmb81ikaEnVLxy]

Hi @Gerardv514,

Sure thing. Please check if this (https://github.com/bitwarden/mobile/issues/2389) is what you are encountering; If not, please feel free to create a Support ticket (https://bitwarden.com/help/) with more details, and we'll have a look.

All the best,

[Cv9kmD9MlsLG9k754vnAPXJC4Dhme6OyG7F7B0l]

I sent a support request about this issue and was sent to this thread.

I would recommend you set up a PIN (https://bitwarden.com/help/unlock-with-pin/) or Biometrics (https://bitwarden.com/help/biometrics/) for now if possible, as a temporary workaround.

FYI Setting up a PIN has not worked for me, I still get asked for master password.

[3JRok3qBTRjKvEhxtgv3R0E9sDwYkY1t1mF5Ai1]

I sent a support request about this issue and was sent to this thread.

I would recommend you set up a PIN (https://bitwarden.com/help/unlock-with-pin/) or Biometrics (https://bitwarden.com/help/biometrics/) for now if possible, as a temporary workaround.

FYI Setting up a PIN has not worked for me, I still get asked for master password.

I have this issue as well.

[RX5ulL6nKunJz88UkudvsdCkM5jkiNQA74LKKeP]

I sent a support request about this issue and was sent to this thread.

I would recommend you set up a PIN (https://bitwarden.com/help/unlock-with-pin/) or Biometrics (https://bitwarden.com/help/biometrics/) for now if possible, as a temporary workaround.

FYI Setting up a PIN has not worked for me, I still get asked for master password.

Agreed I tried pin too and that doesn’t work. For now I’m utilizing Face ID

[RX5ulL6nKunJz88UkudvsdCkM5jkiNQA74LKKeP]

@SergeantConfused has someone been able to reproduce this yet? Is there a need for further information?

[LSUpBlqZjWJUFANDqJbXKEYdx3zbEorkws0ciSV]

I have the same issue with my Android 13 device, it appears to be a clear regression in the 2023.9.1 version of the app, started disregarding my settings (to stay unlocked) and (re)locking the vault/app after some small amount of time, as soon as I upgraded to that app version.

[1iTtuHqbrZxpfu1uAvCAFqXr4n7xvCpwiFpem6q]

Same here.

Setting the PIN does not solve it, still asking for the master pwd on every login autofill.

[ALWfbUHLckzYpe4o22XzYUd9q68UBiKBdDZaWCD]

Same here. IOS 17.0.2, 2023.9.1.

[58lvDUoqfbOC79UZbzVFM2d5PtlFL558JqUpQIb]

I followed this guide to downgrade iOS app to 2023.8.0 where the issue was not present: https://github.com/qnblackcat/How-to-Downgrade-apps-on-AppStore-with-iTunes-and-Charles-Proxy Using build ID 859421181. Hope the fix for this issue could be released soon.

[OH4X7IeIP9W0QpJtvt0LDqe6m8QNXHe08kOKnTb]

Same issue here

[tchuGWED1polKRaffRuAXXuGqg5KEk7ddyPHCYj]

When might I / we expect a fix? This issue has been distressing BW users for way to long. Many weeks.

[SG2miaypK6S8MjNlZTElEujllRbBzfyiK0VSZHx]

I dont want to switch over 1Password however this issue is not acceptable.

[WCSEpkFDjXm1GQknp6OdMHrwtnpUq08pfoqoFrl]

When might I / we expect a fix? This issue has been distressing BW users for way to long. Many weeks.

You think a few weeks is bad, try more than a year as in issue https://github.com/bitwarden/clients/issues/2371

I think BW staff largely ignore GitHub. It might be better to open a support issue on their website. I pay for BW so I might try that route myself.

I dont want to switch over 1Password however this issue is not acceptable.

I tried 1Password earlier this year for a few months and it didn’t even offer an option to not lock the vault after a timeout period, and also prompted every time for pin/biometric when doing autofill.

[n87KPKkoKxYxwrVWqhVzfnFZXYlS9uXHPmdLL2Z]

I think BW staff largely ignore GitHub. It might be better to open a support issue on their website. I pay for BW so I might try that route myself.

Well I put in a ticket a week ago and they just sent me a link to here saying they were already aware of the issue and working on it...

[tAbIkUi4blEAu4VW0M5YzJirfSmb81ikaEnVLxy]

Hello everyone,

Yes, we are able to reproduce this behaviour and are looking into it internally.

As a side note, I've tested using a PIN on iOS 17.0.2 with Bitwarden 2023.9.1, and I am able to unlock my client using that PIN through the Auto-Fill flow. If you are doing this and it's not working, please make sure you tap on (No) when you are asked if you want to require unlocking with your master password when the application is restarted, when you set the PIN up. More about this here (https://bitwarden.com/help/unlock-with-pin/#tab-mobile-DeLAPOlNpLH3MaKazVTfU). If you still are unable to unlock your iOS client using a PIN, please feel free to create a Support ticket (https://bitwarden.com/help/) so we'd have a look because it's probably unrelated to this particular GitHub report.

I thank you in advance for your understanding and patience,

[SG2miaypK6S8MjNlZTElEujllRbBzfyiK0VSZHx]

When might I / we expect a fix? This issue has been distressing BW users for way to long. Many weeks.

You think a few weeks is bad, try more than a year as in issue https://github.com/bitwarden/clients/issues/2371

I think BW staff largely ignore GitHub. It might be better to open a support issue on their website. I pay for BW so I might try that route myself.

I dont want to switch over 1Password however this issue is not acceptable.

I tried 1Password earlier this year for a few months and it didn’t even offer an option to not lock the vault after a timeout period, and also prompted every time for pin/biometric when doing autofill.

There are plenty of security options in 1Password you should check it out again

[wM6uxQiAWZfS8ImVl01QXdjNEDpVGVegMQayeN5]

This also affects Bitwarden 2023.9.1 on Android 11. I hope the problem will be fixed soon.

[d3Lue92Cd254nAWKRjEJO7QR1p2oeJeCBmmLdgn]

Also impacted by the same issue here on Android 13 (GrapheneOS) ever since updating to 2023.9.1. Hopefully there's a fix soon!

[91MHtL5TQT3DhCLzSaSY5BkFupqXQLP8l7ij5gm]

This issue also persists on Android

[elJ1yOqLYZATOqWF185fOcDQb3gFlcGUL95bV1z]

To everyone who has this issue,

downgrade to 2023.8 and don't upgrade.

Downgrade in Android is easy, maybe there's some difficulty for iOS.

[nHFRtfi4Ncs9MmbJALQF9GmwjlWKI3uZTYTxMWA]

Hello. Thank you all for your patience with this very inconvenient behavior as we have been working on a fix. The resolution to this issue is in development and is currently scoped to be included in the next major release. We absolutely understand the urgency and sincerely appreciate your patience.

[KtNg6w7WcAU6vkVxAsYEbnMAkZs41FCN0PZjnD4]

When is the next major release?

[nHFRtfi4Ncs9MmbJALQF9GmwjlWKI3uZTYTxMWA]

@andreacpowers we plan a release in October, but I don't want to commit to an exact date at this point as there are a lot of factors that go in to the exact timing.

[0ZAVh444t2IO0ICOgYfNzKI0cQYe0cYz6l8Gaza]

@Krychaz what's the status of this? More than a dozen people are having issues https://www.reddit.com/r/Bitwarden/comments/16pic4f/bitwarden_always_login_out_after_ios_17/

I'm on Bitwarden app version 2023.9.1 (4890) on iOS 16.6.1

I made a video to showcase this https://www.youtube.com/watch?v=vfYmLvx-gDM

I've seen some older Reddit posts from years ago saying that the phone battery settings matter and whether the app process gets killed https://www.reddit.com/r/Bitwarden/comments/mwgdps/android_bw_keeps_locking/

Though I think this does not apply, since in the video you can see I never closed Safari, I went to fill my login back-to-back and it still required master password re-prompt.

I have my timeout set to never. I've tried logging out of Bitwarden completely and back in. Not working.

[gSAkS2majFeoOqnXwc8XRCH4cXz3Vgkwq8pBJyJ]

@trmartin4, @SergeantConfused, bug is still present on latest release, 2023.9.2 (5102) from 11-Oct. I'm on iOS 17.0.3.

[ALWfbUHLckzYpe4o22XzYUd9q68UBiKBdDZaWCD]

2023.9.2. Still same problem

[tchuGWED1polKRaffRuAXXuGqg5KEk7ddyPHCYj]

2023.9.2 didn’t fix the problem. The problem still exists just as in 3023.9.1

On Thu, Oct 12, 2023 at 12:02 AM Minghao Wang @.***> wrote:

2023.9.2. Still same problem

— Reply to this email directly, view it on GitHub https://github.com/bitwarden/mobile/issues/2787#issuecomment-1758875994, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCZPW4EBDWXJLZ5EUNZ3PJDX65TVRANCNFSM6AAAAAA5DPMB5E . You are receiving this because you commented.Message ID: @.***>

[RX5ulL6nKunJz88UkudvsdCkM5jkiNQA74LKKeP]

The bug still exists because the work to fix it hasn’t been started or merged yet.

[tchuGWED1polKRaffRuAXXuGqg5KEk7ddyPHCYj]

So What Bugs did 2023.9.2 actually try to fix?

On Thu, Oct 12, 2023 at 8:20 AM Gerardv514 @.***> wrote:

The bug still exists because the work to fix it hasn’t been started or merged yet.

— Reply to this email directly, view it on GitHub https://github.com/bitwarden/mobile/issues/2787#issuecomment-1759496330, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCZPW4AEGLZK5QLVOODW7STX67OBFAVCNFSM6AAAAAA5DPMB5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJZGQ4TMMZTGA . You are receiving this because you commented.Message ID: @.***>

[umrTzdU8mXou25Bobxbw98zjVg897Q10F39rJ6Y]

@dickaux

So What Bugs did 2023.9.2 actually try to fix?

you can review the diff here https://github.com/bitwarden/mobile/compare/v2023.9.1...v2023.9.2

[0ZAVh444t2IO0ICOgYfNzKI0cQYe0cYz6l8Gaza]

@djsmith85 any updates on this?

[nHFRtfi4Ncs9MmbJALQF9GmwjlWKI3uZTYTxMWA]

This issue will be included in the next major release (2023.10.0), which is currently undergoing final development in preparation for release later this month. I apologize for the confusion with the 2023.9.2 release - 2023.9.2 was a small, targeted incremental one, and this fix will be included in our planned October release

[0ZAVh444t2IO0ICOgYfNzKI0cQYe0cYz6l8Gaza]

@trmartin4 hm, I hope this isn't too much later in the month. Even when setting vault timeout to 30 minutes rather than Never on mobile app version 2023.9.1 (4890) and iOS version 16.6.1, I have to unlock the Bitwarden vault every single time that I click to fill a login into an app. There's absolutely zero persistence and it's been this way for three weeks. Extremely inconvenient.

[kBhNWxrhwng8b5bHzgY6gMi0uckf4V7bHG6Mrsp]

I don't know if those who are pushing the development are actually paid customers, but as far as I'm aware, this is already a speedy fix, and open source software users are usually willing to wait more patiently, because pushing here won't speed up bug fixing as long as devs have already confirmed that they are working on it. Plus, there are more people subscribing to multiple GitHub issues and only want email notifications when something actually changes...

[G1sFzKsq9dyOYTMycGviY00DfajAbb0mx86LfKN]

To everyone who has this issue,

downgrade to 2023.8 and don't upgrade.

Downgrade in Android is easy, maybe there's some difficulty for iOS.

do you have the steps and link for that version for android thanks

[kBhNWxrhwng8b5bHzgY6gMi0uckf4V7bHG6Mrsp]

@CarlosJoseChaconChavarria If you've installed any APK files manually, then you can just go to this repo's release page to grab the history version you need: https://github.com/bitwarden/mobile/releases/tag/v2023.8.0 As for how to enable manual APK installation, there are many guides floating on the internet...

[0ZAVh444t2IO0ICOgYfNzKI0cQYe0cYz6l8Gaza]

@justindbaur Any updates? More than a month and not resolved. We shouldn't need to manually revert our app version, if that's even possible on iOS, just to fix this. That will probably wipe configuration settings and waste a lot of time. A patch for this has been long awaited. Myself and others have sent details above, including a video. Thanks for your time.

[justindbaur]

@wnelson03 An update was already provided, the fix for this issue will be a part of the 2023.10 release.

[0o4uWG27U6sXwdkLHkkH9ysCLxVFb8UC0fZnHQt]

Not 100% sure, but I believe this PR is what fixes the issue - https://github.com/bitwarden/mobile/pull/2802. As noted above, this was already merged. It looks like new builds are normally out towards the end of the month (seems like the last 2-3 days of the month - going by the past several releases).

[NCEOZv6sD84NTi3bnysvwEVdtlctqrzdyadlIWH]

Still an issue (2023.9.2 on Android). Received email from BitWarden 10/24 that asked to close ticket: "It's been a few days since we last assisted you, we hope your request was resolved to your satisfaction. If you still need help, please reply to this email and we will be glad to continue assisting you. If you no longer need anything for now, there is no need to respond to this message."

Mistake to have migrated from LastPass?

[KtNg6w7WcAU6vkVxAsYEbnMAkZs41FCN0PZjnD4]

Yes, Still an issue (2023.9.2 on Android). I cleared cache and still doesn't work. Lastpass was attacked. 1Password was attacked recently and Bitwarden is terrible. I don't know what to do at this point. Please tell them it's not resolved. I wonder if they even tested.

[kBhNWxrhwng8b5bHzgY6gMi0uckf4V7bHG6Mrsp]

@vrexx1 @andreacpowers Please, people, read. And stop spamming my mailbox.

This issue will be included in the next major release (2023.10.0), which is currently undergoing final development in preparation for release later this month. I apologize for the confusion with the 2023.9.2 release - 2023.9.2 was a small, targeted incremental one, and this fix will be included in our planned October release

[NCEOZv6sD84NTi3bnysvwEVdtlctqrzdyadlIWH]

@escape0707 Re: "spam" you'll need to take that up with support@bitwarden.com.

[elJ1yOqLYZATOqWF185fOcDQb3gFlcGUL95bV1z]

@vrexx1 @andreacpowers Please, people, read. And stop spamming my mailbox.

This issue will be included in the next major release (2023.10.0), which is currently undergoing final development in preparation for release later this month. I apologize for the confusion with the 2023.9.2 release - 2023.9.2 was a small, targeted incremental one, and this fix will be included in our planned October release

You can click the button "Unsubscribe" below, the GitHub will not notice you again. I think the reason why this issue is hot is that people really need the "never timeout" option. Bitwarden is my password manager, i cannot stand that i have to input my another password again every time i want to fill my password via bitwarden. That's really silly and really a problem.

So why people are pushing the developers, it did really impact us.