I’m using Bit Warden (version 2024.7.1) on my iPhone (iOS 17.6.1). First try at login autofill for both the user id and password fields leaves the fields blank. I have to do a second try at autofill for each field and then it works. I’ve looked at the settings and don’t see what I can change that affects this. I just tried changing URI matching from the default to “regular expression”, no change.
Any ideas what can be done about this problem? I’m about ready to change password vault apps, but I really don’t want to do that.
That little issue (I am assuming you are seeing this on one specific website?) certainly wouldn’t be reason for me to switch password managers, but that choice is yours of course.
Every website is constructed differently and while BW does a commendable job of ‘understanding’ them so as to work seamlessly most of the time, it’s not realistic to expect it to work without any little glitches 100% of the time. This to me sounds like a pretty minor issue with one website.
No, I’m seeing this problem everywhere. All logins that I do. I really want to stay with Bit Warden, but this driving me up the wall. Just feels stupid to have to press the same button twice.
I’m currently talking with support, and also checking out 1password. No progress with Bit Warden support yet…nothing useful from them. Hoping for some help, giving them the chance I feel they deserve.
Just a note to add that 1password works perfectly for autologin, first try everytime.
Thinking that I’m going there before too long. It’s just too easy to use. Rather stay with open source, but if it doesn’t work properly on my phone, then I’d be stupid to stay with it, wouldn’t I?
This points to a misconfiguration of your iPhone, or of your entire vault.
Does auto-filling work in a browser, using Bitwarden’s browser extension? On your iPhone, have you followed these instructions?
I’m sorry that others have had problems with 1password. I’ve been using it for a while now, and it’s been fine. Bit Warden fails to function as it is supposed to (and used to) every time. Again, sorry, but that’s the way it is here.
Also, yes, I’ve been using Bit Warden for years, and my iPhone configuration and usage is as the Bit Warden instructions describe. Yes, Bit Warden is working as it was on my desktop browser via the Bit Warden browser extension.
I’m really amazed by this situation, but it is what it is. I’m not lying, I haven’t found a solution for this. As I said I’m talking with support, hoping that they might have access to information that I don’t.
Personally, I’m not so amazed. Simply put, the situation seems to be that your experience (if we take it at face value as you have described it) is highly atypical, which points to a problem that is specific to your setup (e.g., your devices, your software versions, your configuration, and/or your work flow), as opposed to a general problem with the Bitwarden app. Usually, such situations can be resolved, but in an environment like an online forum (or even technical support over email), progress can only be made if the user cooperates and is willing to provide information that is accurate, complete, and sufficiently detailed (to make up for the fact that those trying to assist you have no access to your devices).
Just for the record, the same Bitwarden 2024.7.1 on the same iOS 17.6.1 works normally for me, via the app or the browser extension.
This is near certainly a configuration problem. However, patience for trouble-shooting or to delve into clear information and examples is not universal, and not required if switching feels easier.
I can vouch as well that sometimes on iPhone autofill doesn’t fill, you’ll be prompted for it click it and it doesn’t fill; can do it for multiple tries and the same. I’ve attributed this to when I made the switch to argon2 encryption, ever since then it’s been a problem. Works fine in the browser. For now I just deal with it figuring eventually it’ll get better. If I didn’t keep the timeout of the vault to never, you would see the warning pop up of this and possibly due to the memory or something.
Maybe with this information @MrDoh can advise if he’s using argon2 as encryption.
Quite disappointed how quick MrDoh was dismissed as having some sort of “configuration issue in his iOS.” Honestly it’s pretty basic, if there was a configuration issue it wouldn’t work at all. Additionally if it were some issue with uri matching than it wouldn’t work as they mentioned on other devices. What configurations on iOS would cause having to attempt twice or even multiple times to auto fill.
KDF is a configuration, and it is causing an issue. You shared this important detail in your first comment on this thread, but we know little to nothing about what is happening in OP’s system, even after they posted five comments here.
If it’s a config issue, then what is the proper setting/config to prevent this issue?
To me, it’s not a config issue because if it were we could simply apply the proper config/settings and issue is resolved. A config issue is also something that a user can just simply make changes to and fix. This is a BW issue that needs to be fixed higher up.
I would have also expected the Git issue to have been closed if there was a config issue.
We’re arguing semantics. Of course the KDF issue is a “bug” (or more accurately, an “issue”). But that particular issue is triggered by a specific configuration on iOS devices (including KDF set to Argon2id with high memory cost, and unlock method not set to biometrics).
What happens if you switch your KDF back to PBKDF2, or Argon2id with lower memory setting? What happens if you set you mobile app to unlock with biometrics? Have you tried the procedure described under Item #4 in this comment?
Haven’t tried that as I’m satisfied with my current settings, and can live with the autofill issues in which I hope is short lived a will eventually be fixed.
It’s been a while can’t remember the result when I tried this; it’s documented somewhere. I also have no desire to turn biometrics back on since it slows my workflow, and my phone itself is already protected by biometrics. This is just preference of security vs convenience for me.
No, because I’m not the one with the issue, just merely commented here to provide some sort of support for the user having an issue which was merely dismissed. Having no knowledge of this users’ expertise, my comment here stating my own experience is in hopes of triggering some additional conversation about what could be going on.
This is the main reason why troubleshooting OP’s issue is not going anywhere. They have not been “dismissed” (as you state); the offer to help still stands. However, it is impossible to troubleshoot an issue if the affected user is unwilling to be an active participant in the troubleshooting process.
I concur that the tone on this conversation has room for improvement and I don’t blame @MrDoh for feeling unwelcome. For that I apologize on behalf of us all. Let’s collectively try and keep the conversation both positive and focused on solving the problem at hand.
Auto-fill is not working as expected on his iPhone
He does not experience similar behavior when using 1Password.
He does not experience similar behavior on his desktop using a browser extension.
He has been using Bitwarden for years.
His Bitwarden version and IOS version are current.
Others with similar configuration are not experiencing autofill issues. This gives us hope that @MrDoh’s device can similarly be made to work.
It is notable that the desktop works without issue. This is helpful because it tells us to look towards the iPhone (e.g. as opposed to interactions with the website).
We have seen many instances where reinstalling the app/extension solves odd/unusual problems.
@Gerardv514 indicates that there are apparent issues with Argon2ID. @MrDoh can check if this is set on his vault and if so (temprorarily) change back to PDKDF2 as described here to prove/disprove @Gerardv514’s theory.
Reflect on what else may have changed around the time the problem began. When did you first notice the problem? Shortly before that, did the bitwarden version update, did you get an iOS update, did you changing a setting in Bitwarden, did you install some other extension/app, did you get a new phone, etc?
If Bitwarden support does manage to solve this for you, please report back how the problem was solved. Having the solution documented in the community may help the next unfortunate victim.
Just to keep track of similarities and differences for my working device, I use argon2id also, with settings m=256, t=2, p=3. On a check right now, available RAM on my iPad and iPhone are similar, about 185GB. Working RAM on an iPhone 15 Pro is 8 GB while the older iPad has 6GB. Currently I have enabled biometrics.
Anything else anyone dreams up for me to check or compare, let me know.
An earlier version of this post said I had PIN enabled also. That was incorrect.