Closed 3MN3LoQZMDWcBCOBp4cZqaHEcWlfyIMYXqObzjD closed 3 years ago
Exact same issue. This issue happened after the latest update on iOS.
@NPadrutt can you verify a couple of things for me:
Can you verify keychain autofill is deactivated and Bitwarden is the only application with autofill permission?
After you change your Hotmail password, are you first logging back into the Bitwarden application or going straight to the app extension/autofill service?
@clayadams5226
Yep same sort of situation here. Autofill is showing old passwords despite me deleting them and syncing vault several times.
Same here! iPhone 7 with latest iOS and app version.
As a work around, I've found that uninstalling the app and installing it again seems to resolve this issue.
I tried that but problem persist
Sent from my iPhone
On 7 Jul 2020, at 10:24, Clayton notifications@github.com wrote:
As a work around, I've found that uninstalling the app and installing it again seems to resolve this issue.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/bitwarden/mobile/issues/980#issuecomment-654629220, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APII77XMRYVXSSCX7H3YWTDR2K5SVANCNFSM4N54IXVA.
I have the same problem on my iPhone XR / iOS 13.5.1
Only way to make the new synced passwords show up is restart my phone.
I have the same problem on my iPhone 8 / iOS 13.5.1
Yes I have had the same issue on iPhone7 and latest iOS. I created an account and accepted the strong master password but when I try to log in using the password saved in iOS I receive a wrong password error from Bitwarden. I emailed support and have tried deleting the app and re-installing, but the problem persists. I understand the issue is being looked into.
@NPadrutt Hi there, Nino!
I'm working on fixing this issue for you. It's an odd one - I can get it to repro in some cases .. and not in others. A lot of the time, the resolution thats worked for me is:
I thought I had a resolution - as seen above. But it wasn't the desired solution. I will keep you in the loop on this one. Let me know if the issue still persists as well. Thanks!
Similar issue. iOS 13.5.1 iPhone 8 Plus. Auto-fill password is Bitwarden only, but iCloud Keychain, KeePass Touch and Lass pass are installed.
Created new login entry on PC Firefox extension. Sync'd on PC. Sync'd on iPhone. Can search & find the entry in app, but not with keyboard auto-fill. Searching in the autofill can't locate the new entry by name.
Removed Keepass and Lasspass, rebooted phone. Now that entry is found.
Same issue here. iOS 13.6, iPhone 11 Pro Max, BW 2.5.0 (193). I uninstalled & reinstalled BW and autofill still remembers incorrect data from earlier, before reinstallation!
I normally use Firefox on iOS and autofill using that shows old data. However, if I access same site with Safari and tap the 🔑 button on autofill bar and then "Bitwarden..." autofill data gets updated! So there is some kind of caching, maybe by iOS? Tried with other password manager and it works correctly so this does not look like iOS bug.
@MattTheDev just to give you an update: I just had the same issue with a new entry for twitch. I created the entry on my laptop, closed the twitch on my iPad, synced in bitwarden, switched back to the twitch app and tried to autofill but couldn't find the entry although it was already available in the app.
I also ran into this issue and I may have found the problem.
Like everyone else I've been running into the issue of the auto-fill function of Bitwarden not working on both my iPhone (11 Pro Max @ iOS 13.6 (17G68)) and my iPad (6th Generation @ iOS 13.6 (17G68)).
As suggested here I tried to save a new entry directly into the Bitwarden app and was not able to get it to auto-fill in Firefox (Version 27.0 (18428)), the newly added entry would not populate and searching for it did not work either. I tried closing out both Bitwarden and Firefox and trying again, that did not work. However restarting my phone did work.
With that I did a test. I replicated the issue above by adding a new entry and confirming that it was showing the cached data. I then went to Settings -> Safari -> Clear History and Website Data and this cleared the cache!
I've now tested this on a half dozen different entries to confirm, but clearing the Safari cache works every time, at least for me, that auto-fill starts showing cached data.
Hopefully this helps! I absolutely love this tool and appreciate all the work that goes into making it as great as it is!
I can confirm that the work around of @charles-curran worked for me as well.
I'm having this same issue. Haven't seen anyone mention Android, but I'm running Android 10 on an S10e.
Add an entry via another source and autofill on the app won't have the login information. I have to open the app, sync, and then go back to the login prompt where the auto fill option will be updated.
In the end I deleted the accounts and started again with an externally generated strong password which I then copied to the iOS autofill. Not ideal obviously, but ok for me because the accounts were new and empty anyway.
I read another user emptied the trash and this solved the issue. I tested the approach and after syncing my ios device found the PW stack no longer contained the prior passwords.
Reference:
https://community.bitwarden.com/t/still-using-old-password-on-ios-safari/13226/8
I read another user emptied the trash and this solved the issue. I tested the approach and after syncing my ios device found the PW stack no longer contained the prior passwords.
Reference:
https://community.bitwarden.com/t/still-using-old-password-on-ios-safari/13226/8
Sorry I think this is another issue, the problem described here appears also when the trash is empty
Any updates on this one @MattTheDev? Could you add a force refresh or something in the meantime? Thanks
The affected iPhone was in french and since changing it to english, I no longer get the problem. Could localization be an issue here?
Are people on iOS affected here in a different language as well?
My affected iPhone is in german.
Try switching temporaly to English to see if it resolves the issue you have!
Strange, I have the problem also, and my iPhone is on French
I can’t be sure but what I understand (I’m affected by this bug too) is that there’s the bitwarden process launched by the app, and iOS maintains a separate process for the autofill features. When we change anything in the first process, the second process is not aware. The only workarounds (except not using the Autofill at all) would be whatever method that forces iOS to restart the bw autofill process (I believe it sync on startup), so changing the language (which restarts every app) is a solution, so is restarting the phone or uninstalling the app. If there’s no simple way to control when iOS restarts the autofill process, I guess the only thing bw can do is refresh more often, or refresh on autofill.
For me, it's not a matter of restarting apps/phone, since switching to english I don't have the problem anymore. The 2 commenters below me also have an iPhone with a different than english language though sadly they didn't try to change it it seems, so I'd be interested to see others trying it out.
I also have this issue on my iPhone's (iOS 13 and iOS 14 Beta 8). Going into Settings.app > Safari > Clear History and Website Data resolves it for me.
Note: This seems to affect auto-filling into all apps, not just Safari.
I also have this issue on my iPhone's (iOS 13 and iOS 14 Beta 8). Going into Settings.app > Safari > Clear History and Website Data resolves it for me.
Note: This seems to affect auto-filling into all apps, not just Safari.
I can confirm this worked for me. Does this mean that Safari is actually caching the data and that's being fed to the autofill?
Doesn't that also mean that the data is exposed outside of Bitwarden and stored in Safari Data Cache?
Describe the Bug
I adjusted my Hotmail Password. The password got synced to my iPhone and iPad correctly, but when I autocomplete the password in any password field it fills the wrong one. When I copy and paste it manually it works.
Steps To Reproduce
This was how I did it. Not sure how consistent reproduceable that is
Expected Result
The correct password is filled with Autofill Password
Actual Result
It seems the old password is used in Autofill.
Screenshots or Videos
Environment
Additional Context