Closed 6w6OoPIRf3et9qT8tv7EyO1N5Y6RBqVD0zdY9ih closed 3 years ago
Having the same issue on an iPhone X with iOS 12.1.1 Latest Bitwarden release in the AppStore is v2.2.5
I would really like to ditch my 1Password and use Bitwarden but AutoSync is to important for me.
@Panja0 Well, don’t bother if that’s what you’re waiting for. Synchronisation has never worked properly for me since 2017.
The update they’ve mentioned doesn’t fix it; it merely makes the app sync when manually relogging. So, it’s a workaround for all the sync issues if anything.
That said, Bitwarden is still on version 2.2.5 in the UK.
@StrangePeanut That's a pity to hear. But thanks for mentioning it!
@Panja0 @StrangePeanut
The app now automatically syncs as soon as you unlock the vault. Unless you never lock your vault (which wouldn't make much sense to me to be honest), the new version now solves the problem for most of the people here I guess as you have to unlock anyway. Sure, it would be better if the changes would be pushed to the app immediately, but the experience is actually not much different now.
@chewiesGit What’s your App Store region? If you look through the comments, you’ll see quite a few users do not have access to the update, and no it doesn’t solve the problem in the slightest:
Users shouldn’t have to open the app and log in to get it to sync when other apps can sync in the background just fine. Keep in mind a full sync on login is unnecessarily taxing on your battery too.
The update which most of us have yet to see provides a workaround and not a fix.
@StrangePeanut I am using android. The update was available there immediately.
Sure I've never said it is an ultimate fix. Just wanted to make sure that it is still improving the situation a lot (at least for me). Battery is not really an argument here. I guess your screen is draining a lot more battery while using your synced passwords ;)
On iOS the app is still @ v2.2.5
Therefore, wouldn't the forced sync at login or unlocking be a quick workaround/solution until we find out what the actual problem is?
This is what the app already does. There was a bug in the last version that would cause an issue, however. It should now be resolved in v2.2.6.
On iOS the app is still @ v2.2.5
Yes I was still experiencing this issue, until I figured this out :)
Any word on an iOS update for Bitwarden? We're still on v.2.2.5 and syncing does not work properly.
Still 2.2.5 in the UK App Store. The last update was three months ago!
2.2.5 in Poland still. And this bug still occurs (iPhone 7), unfortunately... 😕
Any progress update on this? I'm running iOS 13.3.1 on an iPhone 7, app version 2.2.5 is still the latest version in the US App Store. To confirm, the issue I am having: The vault on my iOS device does not sync changes/additions made to content from my Mac or the Web Vault unless I manually tap the "Sync Vault Now" button in the iOS app. I have deleted and reinstalled the app, and made sure to Allow push notifications. I am hopeful that: 1) The app will automatically start a sync at Bitwarden app launch with the mentioned 2.2.6 update, 2) Whatever bug is causing the app to not sync new content automatically without any intervention (via push notifications presumably) will be resolved soon as well. Thanks for your hard work!
Seems like we’re waiting for a dev to be hired to update the iOS app.
This thread started over a year ago. This does not bode well for the future of BitWarden. Maybe I should consider going back to 1Password. I don’t want to but if basic issues such as syncing are not resolved quickly then I will lose faith in the long-term viability of this great service.
This thread started over a year ago. This does not bode well for the future of BitWarden. Maybe I should consider going back to 1Password. I don’t want to but if basic issues such as syncing are not resolved quickly then I will lose faith in the long-term viability of this great service.
This is the problem with projects that are mostly maintained by a single person. I would understand if the maintainer was inactive, but it seems like he is just actively ignoring this issue and the fact that iOS apps clearly haven't been updated in all regions.
hello everyone, i found this thread by accident. I've been using BitWarden since December. One of my devices is iphone X with latest IOS, and i have no issues with syncing. it works fine, i even tried to manually to sync under settings and it syncs
Bitwarden v2.3.1 was relased yesterday in the Dutch AppStore. I really got my hopes up... But the same problem remains! :-(
Same as @Panja0 version 2.31 release on the French AppStore. It is a shame that a manual sync as explained here https://github.com/bitwarden/mobile/issues/457#issuecomment-520841886 has not been implemented. It should be en easy workaround which would make many people happy.
Despite this, BitWarden is still the best password manager on the market. 😄
The v2.3.1 update does not address the problem (UK).
What happened to making the app sync on unlock through the long-promised v2.2.6 update that none of us got?
Is this issue still being worked on? Why is it being actively ignored now?
This is a major bug on all mobile platforms.
Each time: a login is recent (< 1-2 weeks), "fill with" is invoked on an input,
Logins are empty and main use case for app is broken.
(Reproduced on Android, iPad)
Same issue here, update a password via the Mac-Chrome extension on my desktop, then try to fill a password via Android App... and it's outdated. I tried locking, etc... nothing seems to automatically or manually sync. This is a very core feature, is there any official response for when this will be resolved?
@mportune-bw I see you self-assigned this in March, good to have you on board! Two questions:
@joallard While there's nothing officially scheduled, we keep sync issues under observation because we have such a difficult time reproducing them... which I guess leads me to your second point - if you've discovered a reliable way to reproduce the issue, we're all ears.
Is there a detailed guide on how to setup a dev environment? Im not a VS guy but want to fix this because it is very annoying. It been nearly 2 years and this isnt fixed. I can reproduce it. If you can provide some guidance on how to properly setup a dev env here (Im coming across so many diff errors on MacOS and as I said I never used VS/Xamarin for mobile app development) one of the community memebers Im sure can fix it.
@mportune-bw ?
Hi @muzzah , VS for Mac makes it pretty easy to work with Xamarin (since it is basically Xamarin Studio renamed); if you want a full local environment; that's a little more challenging, but you should be able to run the mobile app against production if you feel the issue is somewhere in the mobile app code itself. Xamarin has built in emulators and if you're debugging against Android, it's pretty simple... if you're debugging against iOS, there are many articles on setting up Xcode, an Apple Developer account, registering the appropriate certificates for code signing when running locally, and Xcode has pretty nice support for iOS emulators which VS for Mac supports out of the box.
Okay, Now I see different sync issue. Any password updated or deleted in another system/browser is not updating in mobile client autofill. During autofill i still see old/deleted password. This is so annoying lately. Some of my accounts locked out for try trying autofill multiple times with outdated password.
I tried to manually sync through Pull to refresh and Clicking on Sync button, and i see updated password when I manually search but not during autofill.
It seems I have to logout and login for the passwords to be in sync at autofill.
@pavankjadda , are you using v2.7.2?
Yes 2.7.2(401)
This thread started over a year ago. This does not bode well for the future of BitWarden. Maybe I should consider going back to 1Password. I don’t want to but if basic issues such as syncing are not resolved quickly then I will lose faith in the long-term viability of this great service.
I switched to Strongbox instead. Very happy now!
Actually I don't have any sync-issues anymore. Maybe thats why nobody is posting gere lately…
By the way, with the latest version you can enable the manual sync when sliding the finger from top to bottom. To enable it, you must go here: Settings → Sync (in the "MANAGE" section) → Here you got a button to enable this manual sync gesture.
I still have sync issues (now on iOS) but the manual sync made it ok for me to deal with it.
However, and I said that already exactly 2 years ago, the sync issue causes a very problematic security issue in my eyes. Clicking on deauthorizing all sessions in the online vault will not automatically log out all devices (such as the mobile app, the browser extension or the desktop app) until they finally sync and contact the server. I tried it out recently again. After deauthorizing all sessions in the online vault, I was still able to unlock my desktop app (and browser extension), view all my password and work with the app for several minutes until the app finally logged out since it apparently contacted the server. In case i lose my mobile device, for example, I just cannot feel confident that all sessions were indeed deauthorized as they should due to this issue. Is somebody else experiencing this? Did somebody try that out? Would be curious to know if this is happening to others as well.
Or maybe I should consider Strongbox, too...
Well, the main security is a very strong master password (with 2FA). Since, if configured correctly, the Bitwarden vault will be lock after few minutes I don't see where is the problem. 😁 If you got the top security vault in your house but you don't close it before leaving home... For sure, there is a security issue. BTW, on iOS or Android, Bitwarden is always asking my finger print to auto-fill login credentials.
Sure, I know that a securely locked vault is the main security. But why taking the risk? I guess that most people don’t log out every time after using the app, they just lock it, requiring only a finger print or a pin to unlock it. This is the only reason why the deauthorizing function actually exists or was made for. It is supposed to make sure that all devices that are just locked with a pin or finger print (or even unlocked if someone prefers that) get properly logged out. I would just feel much more confident if I knew that all devices are indeed logged out such that the master password as well as 2fa is required to log in, not just a pin or a finger print. I know that there are many risks using a vault like this. But why not eliminating those that we know of and could be eliminated easily. It’s just not very nice to know that a silly bug like this makes the whole thing a bit more unsafe..
I understand your point. AFIK, this bug is only for iOS and, for sure, must be corrected. On the other side (to put the thing in perspective), a malicious person should unlock your iPhone, have you finger print or you Pin code before being able to access the Bitwarden vault. So, again, yes this bug must be fix. However it is not a open hole in the wall. 😉 Bitwarden, to me, IS the best password manager ever (open source code, internet access, plugins for all browsers, apps for all platforms, cheap price for premium and, most important, several external audits said it is safe & secure). IMHO moving to another solution is not the right move. 😋 Strongbox is only for Apple world... Bitwarden is open source and open to all OS. 😁
It at least also exists on MacOS. My iPhone actually syncs much better than the desktop app on my Mac…
Anyway, you are right, it’s not a major security issue. That’s why I am still here after 2 years :) At the same time, I find it a bit frustrating that even after 2 years, nobody seems to take interest in a bug like this. Don’t need to be fixed first thing. But after 2 years?
Well, at the same time I also know myself that deauthorizing wouldn’t have an effect either if somebody just unlocks your vault offline. A real solution to this problem would therefore be when the different apps only work online and show the passwords only after syncing with the server. But that of course is unfeasible as it would mean than one could not view passwords offline..
So I guess in case I lose my phone, I should deauthorize all sessions and at the same time change all existing passwords. So even if somebody somehow unlocked the phone offline (which I know is unlikely but it could happen if someone for example watches entering the pin), they would only see an old version of the vault.
However, that doesn’t mean the sync issue should not be fixed as soon as possible. 😂
I think the Bitwarden dev team is struggling to reproduce the issue. For this kind of bug, 80% of the job is to be able to reproduce the problem.
Today I did some testing on this issue, and it seems to happen if there are two or more Bitwarden apps unlocked and sharing the same external IP.
For example, when my Android phone and my Chromebook are both connected to the same WiFi hotspot, the Android app always syncs (maybe because it uses the Google Cloud Messaging instead of web sockets) but the Chrome extension on the Chromebook fails to sync.
If I lock both and switch my phone to use the 4G network (different IP), everything works as expected.
On the other hand, on my Windows PC, where I often unlock the desktop app, the Chrome and the Edge extensions, I rarely see the syncing to work properly.
Closing this since I don't see this issue from 2.9.2 version
I see this issue in the 2.9.1 version, just reproduced. (iPad)
It seems like 63449a3832478043feb29e2f1a354f6ef4966cc0 is the only change from 2.9.1 to 2.9.2. Did I miss a fix?
Just observed this too in iOS 12 / 2.9.1 Passwords synced only after opening the bitwarden app explicitly.
We are at iOS 16 and I am experiencing the issue for first time in the last three years I have had the service. Of course my subscription is expired. It is being forced by developers?!
update: this is happening on Keeper
the constant uninstall and reinstall - are we developers or chefs?
I didn’t realize an open source application existed for a password manager 🤦🏾♂️
Whenever I add/update a password on a Laptop or Desktop, it’s not automatically syncing to my iPhone even though I authenticate my phone with FaceId. Push notifications are enabled to the app. I am using iOS 12 on iPhone X