Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pre-existing vault file no longer accessible from Google Drive #386

Open
kolole opened this issue Nov 19, 2024 · 5 comments
Open

Pre-existing vault file no longer accessible from Google Drive #386

kolole opened this issue Nov 19, 2024 · 5 comments

Comments

@kolole
Copy link

kolole commented Nov 19, 2024

Bcup version: 2.6.3
Android version: 14
Phone: Google Pixel 6a

First sign of problem
The vault file from Google Drive that was already set (and which was working fine up until recently) could not be opened. The error message could not be read fully, but was repeating, something like "Error, could not fetch: Error could not fetch: Auth Error"

Second sign of problem
After first sign was repeated a bunch of times by unsuccessfully trying to unlock the vault, I deleted all the app data, and tried adding the vault file again. After successfully linking Bcup up to my Google Drive, Bcup can no longer see the vault file that I have indeed saved on the root directory of Google Drive.

Troubleshooting

  • I thought that maybe the file had become corrupted, so I downloaded the vault file and tried opening it on my buttercup-desktop (linux version). That was successful - nothing seemingly wrong with the vault file.

  • In the mobile app, I tried to create a new test vault, which was successful, and the vault file was also saved on the Google Drive.

  • I've also tried to rename the original vault file from within Google Drive, to see if that fixed the issue. No joy.

  • I uploaded a vault file I use on my laptop to Google Drive, but that file can't be seen by Bcup either

Conclusion
Nothing I've tried works. The only way for Bcup to see a vault file located on Google Drive, is to create a new vault from the mobile app - existing vault files on GD are not seen by Bcup Android.

@kolole
Copy link
Author

kolole commented Nov 19, 2024

I see that on Google Drive, Buttercup has the following properties under Security>Your connections to third party apps and services:

Buttercup has some access to your Google Account

Should Buttercup rather be asking to get full access or something? That seems to be right, because the description to "some access" is that the app only has access to the files that were created by the app - but I'm essentially asking it to use files that were not created by this app, at least not this instance of it. I can't change that option, so I think this has to do with what the Buttercup app is requesting to Google.

@kolole
Copy link
Author

kolole commented Nov 19, 2024

This image shows that I have .bcup files on my Google Drive (which the mobile app cannot see)
image

This image shows that bcup mobile cannot see the files
image

This image shows that Buttercup has some (emphasis me) access to my Google Drive
image

@Traimb0t
Copy link

I'm also experiencing this issue and buttercup has become unusable on Android.

@vpelaez
Copy link

vpelaez commented Nov 27, 2024

This is also happening to me in iOS

@kolole

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants