Closed catcake closed 2 years ago
I have added the vault to the mobile app again under the name "main2"; it is identical to the vault the desktop clients see, while the original vault ("main") is still desynced.
I'm going to work around this issue by manually copying the updates from main to main2. Any idea how to prevent this from happening again?
Thanks, cat
@catcake does the issue still exist with the latest version of Buttercup mobile (2.1.0) ?
I don't know. I logged into gdrive again thru the app and resynced the vault and haven't had any problems since. I still had the original vault, which still didn't work, up until the new update when all vaults cleared and had to be synced again.
Closing this for now. If we find a reproducible case of this I'll happily reopen.
For this to be considered as an issue to be debugged, I'd need a dummy vault that shows these signs and instructions on how to reproduce the issue.
Describe the issue you're having The mobile client appears to not be pushing updates to a Google Drive vault.
What were you doing when the issue occurred? How do we reproduce it?
I had just added an OTP property to an existing entry for a Microsoft account and shortly afterwards checked the desktop client for a OTP code, and discovering that the new OTP property was not present.
Versions/Devices
Buttercup version information: Desktop @ v2.10.0 Core @ v6.0.0 Flags: installed
Operating System: Arch Linux
Kernel: Linux 5.14.6-arch1-1
Buttercup version information: Desktop @ v2.10.0 Core @ v6.0.0 Flags: installed
Android version 11 Android security update September 5, 2021 Google Play system update August 1, 2021
Buttercup app version 1.16.0