You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile
Steps To Reproduce
Keep the app open in the foreground.
Make a change in web vault, e.g. change the name of a folder.
Server pushes the change to clients.
Expected Result
The change is reflected in the app within a few seconds.
Actual Result
The change is not synced unless manually refreshed.
Screenshots or Videos
Bitwarden_Auto_Sync_Issue_Demo_bitwarden_com.mp4
Additional Context
Auto sync is working on the current legacy app (2024.7.1). Same behavior on bitwarden.com and self-hosted Vaultwarden.
Build Version
2024.8.0 (284)
Environment Details
Tested on
Device: iPhone 15 Pro Max
OS Version: iOS 18.1 Dev Beta 2 (22B5023e)
and
Device: iPad Pro M4 (2024) 13-inch
OS Version: iOS 17.6.1
Issue Tracking Info
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
I was able to reproduce this issue, and I have flagged this 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.
Bitwarden Beta
Steps To Reproduce
Expected Result
The change is reflected in the app within a few seconds.
Actual Result
The change is not synced unless manually refreshed.
Screenshots or Videos
Bitwarden_Auto_Sync_Issue_Demo_bitwarden_com.mp4
Additional Context
Auto sync is working on the current legacy app (2024.7.1). Same behavior on bitwarden.com and self-hosted Vaultwarden.
Build Version
2024.8.0 (284)
Environment Details
Tested on
and
Issue Tracking Info
The text was updated successfully, but these errors were encountered: