Vault timeout option not respected on iOS #1729

@Gerardv514 commented on GitHub (Sep 23, 2023):

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

@Gerardv514 commented on GitHub (Sep 23, 2023): 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

GiteaMirror commented

@quagsirus commented on GitHub (Sep 23, 2023):

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.

@quagsirus commented on GitHub (Sep 23, 2023): 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.

GiteaMirror commented

@SergeantConfused commented on GitHub (Sep 23, 2023):

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,

@SergeantConfused commented on GitHub (Sep 23, 2023): 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,

GiteaMirror commented

@Gerardv514 commented on GitHub (Sep 23, 2023):

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.

@Gerardv514 commented on GitHub (Sep 23, 2023): 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.

GiteaMirror commented

@SergeantConfused commented on GitHub (Sep 23, 2023):

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,

@SergeantConfused commented on GitHub (Sep 23, 2023): 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,

GiteaMirror commented

@Gerardv514 commented on GitHub (Sep 23, 2023):

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

@Gerardv514 commented on GitHub (Sep 23, 2023): 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

GiteaMirror commented

2025-11-26 22:56:31 -06:00

@SergeantConfused commented on GitHub (Sep 23, 2023):

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,

@SergeantConfused commented on GitHub (Sep 23, 2023): 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,

GiteaMirror commented

@colleenmason commented on GitHub (Sep 26, 2023):

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.

@colleenmason commented on GitHub (Sep 26, 2023): 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.

GiteaMirror commented

2025-11-26 22:56:31 -06:00

@ryanpcmcquen commented on GitHub (Sep 26, 2023):

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.

@ryanpcmcquen commented on GitHub (Sep 26, 2023): > 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.

GiteaMirror commented

2025-11-26 22:56:31 -06:00

@Gerardv514 commented on GitHub (Sep 26, 2023):

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

@Gerardv514 commented on GitHub (Sep 26, 2023): > 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

GiteaMirror commented

@Gerardv514 commented on GitHub (Sep 27, 2023):

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

@Gerardv514 commented on GitHub (Sep 27, 2023): @SergeantConfused has someone been able to reproduce this yet? Is there a need for further information?

GiteaMirror commented

@thefutureofwhat commented on GitHub (Sep 27, 2023):

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.

@thefutureofwhat commented on GitHub (Sep 27, 2023): 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.

GiteaMirror commented

@xavirg commented on GitHub (Sep 27, 2023):

Same here.

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

@xavirg commented on GitHub (Sep 27, 2023): Same here. Setting the PIN does not solve it, still asking for the master pwd on every login autofill.

GiteaMirror commented

@MinghaoUpUpUp commented on GitHub (Sep 27, 2023):

Same here. IOS 17.0.2, 2023.9.1.

@MinghaoUpUpUp commented on GitHub (Sep 27, 2023): Same here. IOS 17.0.2, 2023.9.1.

GiteaMirror commented

@keldey commented on GitHub (Sep 29, 2023):

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.

@keldey commented on GitHub (Sep 29, 2023): 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](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.

GiteaMirror commented

@feux-follets commented on GitHub (Sep 30, 2023):

Same issue here

@feux-follets commented on GitHub (Sep 30, 2023): Same issue here

GiteaMirror commented

@dickaux commented on GitHub (Sep 30, 2023):

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

@dickaux commented on GitHub (Sep 30, 2023): When might I / we expect a fix? This issue has been distressing BW users for way to long. Many weeks.

GiteaMirror commented

@muhasturk commented on GitHub (Oct 1, 2023):

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

@muhasturk commented on GitHub (Oct 1, 2023): I dont want to switch over 1Password however this issue is not acceptable.

GiteaMirror commented

@ahsodex commented on GitHub (Oct 1, 2023):

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.

@ahsodex commented on GitHub (Oct 1, 2023): > 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.

GiteaMirror commented

@madmatt347 commented on GitHub (Oct 1, 2023):

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...

@madmatt347 commented on GitHub (Oct 1, 2023): > 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...

GiteaMirror commented

@SergeantConfused commented on GitHub (Oct 1, 2023):

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,

@SergeantConfused commented on GitHub (Oct 1, 2023): 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,

GiteaMirror commented

@muhasturk commented on GitHub (Oct 1, 2023):

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

@muhasturk commented on GitHub (Oct 1, 2023): > > 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 ![image](https://github.com/bitwarden/mobile/assets/4077401/9ebdf43b-c32d-4ecd-a6a5-095790bc8fed)

GiteaMirror commented

@yoshi-sheep commented on GitHub (Oct 2, 2023):

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

@yoshi-sheep commented on GitHub (Oct 2, 2023): This also affects Bitwarden 2023.9.1 on Android 11. I hope the problem will be fixed soon.

GiteaMirror commented

@celenityy commented on GitHub (Oct 3, 2023):

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

@celenityy commented on GitHub (Oct 3, 2023): Also impacted by the same issue here on Android 13 (GrapheneOS) ever since updating to 2023.9.1. Hopefully there's a fix soon!

GiteaMirror commented

@Slash8915 commented on GitHub (Oct 4, 2023):

This issue also persists on Android

@Slash8915 commented on GitHub (Oct 4, 2023): This issue also persists on Android

GiteaMirror commented

@MeteorsLiu commented on GitHub (Oct 5, 2023):

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.

@MeteorsLiu commented on GitHub (Oct 5, 2023): 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.

GiteaMirror commented

@trmartin4 commented on GitHub (Oct 7, 2023):

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.

@trmartin4 commented on GitHub (Oct 7, 2023): 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.

GiteaMirror commented

@andreacpowers commented on GitHub (Oct 7, 2023):

When is the next major release?

@andreacpowers commented on GitHub (Oct 7, 2023): When is the next major release?

GiteaMirror commented

2025-11-26 22:56:36 -06:00

@trmartin4 commented on GitHub (Oct 8, 2023):

@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.

@trmartin4 commented on GitHub (Oct 8, 2023): @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.

GiteaMirror commented

@wnelson03 commented on GitHub (Oct 10, 2023):

@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.

@wnelson03 commented on GitHub (Oct 10, 2023): @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 <ins>**does not apply**</ins>, 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.

GiteaMirror commented

2025-11-26 22:56:36 -06:00

@swderek commented on GitHub (Oct 11, 2023):

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

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

GiteaMirror commented

2025-11-26 22:56:37 -06:00

@MinghaoUpUpUp commented on GitHub (Oct 12, 2023):

2023.9.2. Still same problem

@MinghaoUpUpUp commented on GitHub (Oct 12, 2023): 2023.9.2. Still same problem

GiteaMirror commented

2025-11-26 22:56:37 -06:00

@dickaux commented on GitHub (Oct 12, 2023):

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:
@.***>

@dickaux commented on GitHub (Oct 12, 2023): 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: > ***@***.***> >

GiteaMirror commented

2025-11-26 22:56:37 -06:00

@Gerardv514 commented on GitHub (Oct 12, 2023):

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

@Gerardv514 commented on GitHub (Oct 12, 2023): The bug still exists because the work to fix it hasn’t been started or merged yet.

GiteaMirror commented

@dickaux commented on GitHub (Oct 12, 2023):

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:
@.***>

@dickaux commented on GitHub (Oct 12, 2023): 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: > ***@***.***> >

GiteaMirror commented

@0xadada commented on GitHub (Oct 12, 2023):

@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

@0xadada commented on GitHub (Oct 12, 2023): @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

GiteaMirror commented

@wnelson03 commented on GitHub (Oct 15, 2023):

@djsmith85 any updates on this?

@wnelson03 commented on GitHub (Oct 15, 2023): @djsmith85 any updates on this?

GiteaMirror commented

@trmartin4 commented on GitHub (Oct 16, 2023):

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

@trmartin4 commented on GitHub (Oct 16, 2023): 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

GiteaMirror commented

@wnelson03 commented on GitHub (Oct 16, 2023):

@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.

@wnelson03 commented on GitHub (Oct 16, 2023): @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.

GiteaMirror commented

@escape0707 commented on GitHub (Oct 16, 2023):

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...

@escape0707 commented on GitHub (Oct 16, 2023): 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...

GiteaMirror commented

@CarlosJoseChaconChavarria commented on GitHub (Oct 18, 2023):

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

@CarlosJoseChaconChavarria commented on GitHub (Oct 18, 2023): > 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

GiteaMirror commented

@escape0707 commented on GitHub (Oct 18, 2023):

@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...

@escape0707 commented on GitHub (Oct 18, 2023): @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...

GiteaMirror commented

@wnelson03 commented on GitHub (Oct 23, 2023):

@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.

@wnelson03 commented on GitHub (Oct 23, 2023): @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.

GiteaMirror commented

@justindbaur commented on GitHub (Oct 23, 2023):

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

@justindbaur commented on GitHub (Oct 23, 2023): @wnelson03 An update was already provided, the fix for this issue will be a part of the `2023.10` release.

GiteaMirror commented

@breakthestatic commented on GitHub (Oct 23, 2023):

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).

@breakthestatic commented on GitHub (Oct 23, 2023): 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).

GiteaMirror commented

@vrexx1 commented on GitHub (Oct 24, 2023):

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?

@vrexx1 commented on GitHub (Oct 24, 2023): 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?

GiteaMirror commented

@andreacpowers commented on GitHub (Oct 24, 2023):

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.

@andreacpowers commented on GitHub (Oct 24, 2023): 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.

GiteaMirror commented

@escape0707 commented on GitHub (Oct 25, 2023):

@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

@escape0707 commented on GitHub (Oct 25, 2023): @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

GiteaMirror commented

@vrexx1 commented on GitHub (Oct 25, 2023):

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

@vrexx1 commented on GitHub (Oct 25, 2023): @escape0707 Re: "spam" you'll need to take that up with support@bitwarden.com.

GiteaMirror commented

@MeteorsLiu commented on GitHub (Oct 25, 2023):

@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.

@MeteorsLiu commented on GitHub (Oct 25, 2023): > @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.

GiteaMirror commented

@wnelson03 commented on GitHub (Oct 25, 2023):

Yeah @justindbaur why wait all the way to the end of the month for a fix that could be implemented in less than a day? Seems pretty clear this is greatly inconveniencing people. It's not a feature, it's a fix to bug that has been unresolved for a month..

@wnelson03 commented on GitHub (Oct 25, 2023): Yeah @justindbaur why wait all the way to the end of the month for a fix that could be implemented in less than a day? Seems pretty clear this is greatly inconveniencing people. It's not a feature, it's a fix to bug that has been unresolved for a month..

GiteaMirror commented

@djsmith85 commented on GitHub (Oct 25, 2023):

Closing this now.

As previously mentioned a fix will be included in the upcoming 2023.10-release, which is currently targeted to be released next week.

@djsmith85 commented on GitHub (Oct 25, 2023): Closing this now. As previously mentioned a fix will be included in the upcoming `2023.10`-release, which is currently targeted to be released next week.

GiteaMirror commented

@jidanni commented on GitHub (Oct 29, 2023):

Just curious as what happens/happened to passwords of new accounts (on websites/apps we browsed, vault locked) created while this bug is/was present? Not remembered and lost forever?

@jidanni commented on GitHub (Oct 29, 2023): Just curious as what happens/happened to passwords of new accounts (on websites/apps we browsed, vault locked) created while this bug is/was present? Not remembered and lost forever?

GiteaMirror commented

@Voykimmer commented on GitHub (Oct 31, 2023):

Well a fix was supposed to be out the end of October with 2023.10 . Well today is the end of October and still no fix. What gives ? Am I going to have to move to another password manager again ?

@Voykimmer commented on GitHub (Oct 31, 2023): Well a fix was supposed to be out the end of October with 2023.10 . Well today is the end of October and still no fix. What gives ? Am I going to have to move to another password manager again ?

GiteaMirror commented

@wnelson03 commented on GitHub (Oct 31, 2023):

In my opinion, they're probably working on it and will release within a few days, probably first week of November.

However, I just don't understand why wait & put such a prevalent bug fix in a major release. It's a bug that is clearly impacting several people. Seems like it would make more sense to just release the bug fix ahead of the release.

Love the open source part of Bitwarden, but in terms of improving customer satisfaction there could definitely be more transparency to do with the bug and feature request process. It seems status updates are seldom in bug reports and feature requests, and it can be very frustrating seeing how slow things move.

Just trying to explain what I think could be done better. No disrespect meant towards the Bitwarden team.

@wnelson03 commented on GitHub (Oct 31, 2023): In my opinion, they're probably working on it and will release within a few days, probably first week of November. However, I just don't understand why wait & put such a prevalent bug fix in a major release. It's a bug that is clearly impacting several people. Seems like it would make more sense to just release the bug fix ahead of the release. Love the open source part of Bitwarden, but in terms of improving customer satisfaction there could definitely be more transparency to do with the bug and feature request process. It seems status updates are seldom in bug reports and feature requests, and it can be very frustrating seeing how slow things move. Just trying to explain what I think could be done better. No disrespect meant towards the Bitwarden team.

GiteaMirror commented

@0xadada commented on GitHub (Oct 31, 2023):

@Voykimmer

Well a fix was supposed to be out the end of October with 2023.10 . Well today is the end of October and still no fix. What gives ? Am I going to have to move to another password manager again ?

@wnelson03

just don't understand why wait & put such a prevalent bug fix in a major release.

The release process is more than just merging a fix PR and running a build. There are multiple engineering teams involved, multiple platforms (Safari/Chrome/Firefox x iOS/Windows x Desktop/Mobile, etc), and multiple AppStores (Google Play, AppStore, etc), marketing, coms, etc that all need to be coordinated.

@0xadada commented on GitHub (Oct 31, 2023): @Voykimmer > Well a fix was supposed to be out the end of October with 2023.10 . Well today is the end of October and still no fix. What gives ? Am I going to have to move to another password manager again ? @wnelson03 > just don't understand why wait & put such a prevalent bug fix in a major release. The release process is more than just merging a fix PR and running a build. There are multiple engineering teams involved, multiple platforms (Safari/Chrome/Firefox x iOS/Windows x Desktop/Mobile, etc), and multiple AppStores (Google Play, AppStore, etc), marketing, coms, etc that all need to be coordinated.

GiteaMirror commented

@wnelson03 commented on GitHub (Oct 31, 2023):

The release process is more than just merging a fix PR and running a build. There are multiple engineering teams involved, multiple platforms (Safari/Chrome/Firefox x iOS/Windows x Desktop/Mobile, etc), and multiple AppStores (Google Play, AppStore, etc), marketing, coms, etc that all need to be coordinated.

@0xadada I get that, though they're intentionally holding off on the production release of the bug fix until they have finished other features and likely less important bugs. This bug report has been open for 1+ month(s), rolling out solely a bug fix does not take 1 month.

So yes, I understand why a whole release in its entirety would take a while. I wish they spent more time testing their last release so this bug didn't even get introduced. However, once you have a bug that is showing to affect several dozens of people on Reddit & GitHub, it seems to make sense to roll that out on its own rather than waiting until the next big release.

@wnelson03 commented on GitHub (Oct 31, 2023): > The release process is more than just merging a fix PR and running a build. There are multiple engineering teams involved, multiple platforms (Safari/Chrome/Firefox x iOS/Windows x Desktop/Mobile, etc), and multiple AppStores (Google Play, AppStore, etc), marketing, coms, etc that all need to be coordinated. @0xadada I get that, though they're intentionally holding off on the production release of the bug fix until they have finished other features and likely less important bugs. This bug report has been open for 1+ month(s), rolling out solely a bug fix does not take 1 month. So yes, I understand why a whole release in its entirety would take a while. I wish they spent more time testing their last release so this bug didn't even get introduced. However, once you have a bug that is showing to affect several dozens of people on Reddit & GitHub, it seems to make sense to roll that out on its own rather than waiting until the next big release.

GiteaMirror commented

@escape0707 commented on GitHub (Oct 31, 2023):

I just don't understand why wait & put such a prevalent bug fix in a major release.

Because usually when developers fix a bug, they will first implement the fix at the current developing branch. That fix usually can't be simply copy-pasted to older releases because there are code differences between them. Only when an issue is serious enough or the developing force is just too rich will it be back-ported to a previous release, and effectively doubles the time needed for Quality Assessment.

Just for the reference, here is an even more annoying Firefox bug currently in Firefox 119 release, but Mozilla didn't choose to back-port the fix to 119, either.

@escape0707 commented on GitHub (Oct 31, 2023): > I just don't understand why wait & put such a prevalent bug fix in a major release. Because usually when developers fix a bug, they will first implement the fix at the current developing branch. That fix usually can't be simply copy-pasted to older releases because there are code differences between them. Only when an issue is serious enough or the developing force is just too rich will it be back-ported to a previous release, and effectively doubles the time needed for Quality Assessment. Just for the reference, [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1859945) is an even more annoying Firefox bug currently in Firefox 119 release, but Mozilla didn't choose to back-port the fix to 119, either.

GiteaMirror commented

2025-11-26 22:56:43 -06:00

@wnelson03 commented on GitHub (Oct 31, 2023):

Just for the reference, here is an even more annoying Firefox bug currently in Firefox 119 release, but Mozilla didn't choose to back-port the fix to 119, either.

This is an important usability issue that has impacted dozens of people here and on Reddit. Sure, it might be somewhat of an inconvenience to have to separately merge in code to fix a bug, though this bug is entirely dependent on Bitwarden publishing a release without enough testing. Not a user error or something that can really be fixed by a user behavior.

I'm not sure how you could say that Firefox bug is "even more annoying". It looks to me to be a minor appearance flaw. And Mozilla might not even be entirely responsible. That Tesla website in the GitHub issue is probably at fault for setting a custom HTML background rather than letting the browser default take precedence. Not sure though. Regardless, you're comparing an issue with Bitwarden that at best case wastes a lot of time when we're out somewhere needing to login to a website quickly, and at worse case could cause someone to not be able to access their account at all for the moment if they don't remember their entire passphrase if it's very long.

Comparing that to Firefox showing a color you don't particularly like.. Apples to Oranges.

@wnelson03 commented on GitHub (Oct 31, 2023): > Just for the reference, [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1859945) is an even more annoying Firefox bug currently in Firefox 119 release, but Mozilla didn't choose to back-port the fix to 119, either. This is an important usability issue that has impacted dozens of people here and on [Reddit](https://www.reddit.com/r/Bitwarden/comments/16pic4f/bitwarden_always_login_out_after_ios_17/). Sure, it might be somewhat of an inconvenience to have to separately merge in code to fix a bug, though this bug is entirely dependent on Bitwarden publishing a release without enough testing. Not a user error or something that can really be fixed by a user behavior. I'm not sure how you could say that Firefox bug is "even more annoying". It looks to me to be a minor appearance flaw. And Mozilla might not even be entirely responsible. That Tesla website in the GitHub issue is probably at fault for setting a custom HTML background rather than letting the browser default take precedence. Not sure though. Regardless, you're comparing an issue with Bitwarden that at best case wastes a lot of time when we're out somewhere needing to login to a website quickly, and at worse case could cause someone to not be able to access their account at all for the moment if they don't remember their entire passphrase if it's very long. Comparing that to Firefox showing a color you don't particularly like.. Apples to Oranges.

GiteaMirror commented

@escape0707 commented on GitHub (Oct 31, 2023):

The annoyance of the white flash even with dark reader and dark theme is described in this thread https://github.com/darkreader/darkreader/issues/11190#issuecomment-1737877948

@escape0707 commented on GitHub (Oct 31, 2023): The annoyance of the white flash even with dark reader and dark theme is described in this thread https://github.com/darkreader/darkreader/issues/11190#issuecomment-1737877948

GiteaMirror commented

2025-11-26 22:56:43 -06:00

@wnelson03 commented on GitHub (Oct 31, 2023):

The annoyance of the white flash even with dark reader and dark theme is described in this thread darkreader/darkreader#11190 (comment)

Yeah you're seriously comparing getting logged out after every single unlock to an undesirable color on your screen..

The open-source side of Bitwarden is awesome. But that doesn't mean they're a super small company. In case you aren't aware, Bitwarden is a very large company with supposedly 108 employees. They've also raised $100 million in funding from just one funding round.

So, they certainly have the resources to respond quicker, have people that provide the customers with status updates, and people who get paid to deal with the inconvenience of separately merging code to fix a problem they created themselves.

I just haven't quite been satisfied with:

The long duration of time it takes for a reported bug or feature request to be completed
The lack of status updates given to the customers in between the time the bug report or feature request was made

I understand that the subscription isn't pricey at all and that they probably make most of their money from enterprise business customers and must delegate the majority of their resources to that. But c'mon it has taken notifying 4-5 Bitwarden employees on Pull Requests before there is ever a response from one of them. It's very frustrating and kind of diminishes the point of making pull requests or other contributions knowing that they sit in limbo for months, sometimes years with some of the Pull Requests I've seen before getting merged.

@wnelson03 commented on GitHub (Oct 31, 2023): > The annoyance of the white flash even with dark reader and dark theme is described in this thread [darkreader/darkreader#11190 (comment)](https://github.com/darkreader/darkreader/issues/11190#issuecomment-1737877948) Yeah you're seriously comparing getting logged out after every single unlock to an undesirable color on your screen.. The open-source side of Bitwarden is awesome. But that doesn't mean they're a super small company. In case you aren't aware, Bitwarden is a very large company with [supposedly 108 employees](https://www.zoominfo.com/c/bitwarden-inc/447031277). They've also raised [$100 million in funding](https://techcrunch.com/2022/09/06/open-source-password-manager-bitwarden-raises-100m/) from just one funding round. So, they certainly have the resources to respond quicker, have people that provide the customers with status updates, and people who get paid to deal with the inconvenience of separately merging code to fix a problem they created themselves. I just haven't quite been satisfied with: 1) The long duration of time it takes for a reported bug or feature request to be completed 2) The lack of status updates given to the customers in between the time the bug report or feature request was made I understand that the subscription isn't pricey at all and that they probably make most of their money from enterprise business customers and must delegate the majority of their resources to that. But c'mon it has taken notifying 4-5 Bitwarden employees on Pull Requests before there is ever a response from one of them. It's very frustrating and kind of diminishes the point of making pull requests or other contributions knowing that they sit in limbo for months, sometimes years with some of the Pull Requests I've seen before getting merged.

GiteaMirror commented

2025-11-26 22:56:43 -06:00

@muhasturk commented on GitHub (Nov 2, 2023):

2023.10.0 release hasn't fixed. this issue when using auto fill feature, it asks to enter master password every time.
iOS 16.7.2

@muhasturk commented on GitHub (Nov 2, 2023): 2023.10.0 release hasn't fixed. this issue when using auto fill feature, it asks to enter master password every time. iOS 16.7.2

GiteaMirror commented

@wnelson03 commented on GitHub (Nov 2, 2023):

2023.10.0 release hasn't fixed. this issue when using auto fill feature, it asks to enter master password every time. iOS 16.7.2

So far working well for me. It seems that it reset my vault timeout settings for some reason though. So you should probably go into the Bitwarden app, go to settings tab, and set vault timeout to Never. Then it worked.

@wnelson03 commented on GitHub (Nov 2, 2023): > 2023.10.0 release hasn't fixed. this issue when using auto fill feature, it asks to enter master password every time. iOS 16.7.2 So far working well for me. It seems that it reset my vault timeout settings for some reason though. So you should probably go into the Bitwarden app, go to settings tab, and set vault timeout to Never. Then it worked.

GiteaMirror commented

@andreacpowers commented on GitHub (Nov 2, 2023):

Not updated for Android yet.
Reminder to check each place you have Bitwarden: extensions on each browser, app on phone.

@andreacpowers commented on GitHub (Nov 2, 2023): Not updated for Android yet. Reminder to check each place you have Bitwarden: extensions on each browser, app on phone.

GiteaMirror commented

@sinamics commented on GitHub (Nov 2, 2023):

when will the android version be out?

@sinamics commented on GitHub (Nov 2, 2023): when will the android version be out?

GiteaMirror commented

@wnelson03 commented on GitHub (Nov 2, 2023):

@andreacpowers @sinamics Google may still be reviewing the play store release.

"App review times may fluctuate, and may take 7 days or longer in exceptional cases" https://support.google.com/googleplay/android-developer/thread/207283574/the-app-is-taking-long-time-in-review?hl=en

Strange thing is that the Play store website shows that it was updated yesterday on November 1st but then the version is still outdated. Perhaps that means the release was submitted for review yesterday but it will stay on the old version until the employees at Google approve the release of the new version.

@wnelson03 commented on GitHub (Nov 2, 2023): @andreacpowers @sinamics Google may still be reviewing the play store release. "App review times may fluctuate, and may take 7 days or longer in exceptional cases" https://support.google.com/googleplay/android-developer/thread/207283574/the-app-is-taking-long-time-in-review?hl=en Strange thing is that the Play store website shows that it was updated yesterday on November 1st but then the version is still outdated. Perhaps that means the release was submitted for review yesterday but it will stay on the old version until the employees at Google approve the release of the new version. ![image](https://github.com/bitwarden/mobile/assets/83034852/efab5284-d65f-4d16-a6d9-49820e4baf10)

GiteaMirror commented

@Voykimmer commented on GitHub (Nov 2, 2023):

my iPad and iPhone still at
Version: 2023.9.2 (5102) and no update available yet and Bitwarden is still broken.

@Voykimmer commented on GitHub (Nov 2, 2023): my iPad and iPhone still at Version: 2023.9.2 (5102) and no update available yet and Bitwarden is still broken.

GiteaMirror commented

@wnelson03 commented on GitHub (Nov 2, 2023):

my iPad and iPhone still at Version: 2023.9.2 (5102) and no update available yet and Bitwarden is still broken.

Interesting, I'm on iOS 16.6.1 with iPhone 13 and I saw the Update button in the app store and updated. Then I had to change vault timeout to Never again since for some reason that setting was reset. Then it worked.

@wnelson03 commented on GitHub (Nov 2, 2023): > my iPad and iPhone still at Version: 2023.9.2 (5102) and no update available yet and Bitwarden is still broken. Interesting, I'm on iOS 16.6.1 with iPhone 13 and I saw the Update button in the app store and updated. Then I had to change vault timeout to _Never_ again since for some reason that setting was reset. Then it worked.

GiteaMirror commented

@Voykimmer commented on GitHub (Nov 2, 2023):

I’m at IOS 16.7.2 on both my iPhone 8 and my
iPad (6th generation) and no update has been pushed to either yet .

@Voykimmer commented on GitHub (Nov 2, 2023): I’m at IOS 16.7.2 on both my iPhone 8 and my iPad (6th generation) and no update has been pushed to either yet .

GiteaMirror commented

@muhasturk commented on GitHub (Nov 2, 2023):

video proof

@muhasturk commented on GitHub (Nov 2, 2023): [video proof](https://youtube.com/shorts/BvJSo__2rBY?si=9VPpX2In785DQlSR)

GiteaMirror commented

@Gerardv514 commented on GitHub (Nov 2, 2023):

video proof

Can you turn off the option “ unlock with Face ID” and keep vault time out set to never again.

My issue has been resolved.

@Gerardv514 commented on GitHub (Nov 2, 2023): > [video proof](https://youtube.com/shorts/BvJSo__2rBY?si=9VPpX2In785DQlSR) Can you turn off the option “ unlock with Face ID” and keep vault time out set to never again. My issue has been resolved.

GiteaMirror commented

@madmatt347 commented on GitHub (Nov 3, 2023):

Update to 2023.10.0 fixed the issue for me on Android 5.1

Thanks Devs

@madmatt347 commented on GitHub (Nov 3, 2023): Update to 2023.10.0 fixed the issue for me on Android 5.1 Thanks Devs

GiteaMirror commented

@Voykimmer commented on GitHub (Nov 3, 2023):

I deleted the Bitwarden app and downloaded and reinstalled from the App Store and I got 2023-10 and now everything works great. You do have to go in the settings and change timeout to never again tho.

@Voykimmer commented on GitHub (Nov 3, 2023): I deleted the Bitwarden app and downloaded and reinstalled from the App Store and I got 2023-10 and now everything works great. You do have to go in the settings and change timeout to never again tho.

GiteaMirror commented

@jidanni commented on GitHub (Nov 6, 2023):

~~No update if you are an Android beta tester.~~
Beta update arrived 2023/11/09 . Good.

@jidanni commented on GitHub (Nov 6, 2023): ![Screenshot_20231106_092141_Google Play Store.jpg](https://github.com/bitwarden/mobile/assets/1230959/967a6f1f-5897-4624-a73f-6577a4a7780b) ~~No update if you are an Android beta tester.~~ Beta update arrived 2023/11/09 . Good.

GiteaMirror commented

@Swap-File commented on GitHub (Nov 8, 2023):

Fixed as of yesterday on Android.

@Swap-File commented on GitHub (Nov 8, 2023): Fixed as of yesterday on Android.

GiteaMirror commented