Unable to open .bcup file from Google Drive about buttercup-desktop HOT 6 CLOSED

I can confirm that, I had the same problem with my windows computer and I found a workaround :

• download the "old" file and open it in local with bcup by creating a new vault.
• export it in csv buttercup file
• create a new empty vault on drive
• import the local csv file
  The new bcup file is now visible in the list when adding a new one.

But on linux (Ubuntu 20.04.6 LTS) I am stuck after google authentication, the magnet link is not opening & the desktop app still asking for login. (tried 3 browsers)
The only error in terminal after init is : Failed registering protocol: buttercup
Should I create a new issue ?

Thx

Edit: I just figured out that this does not export OTP codes, I there a way to do that ?
Edit2: After researches it exports OTP but into a field otpauth://totp/xxxxxx (no longer visible as a code)

from buttercup-desktop.

Perhaps one was not added using Buttercup, and uploaded manually? We recently had to drop our restricted Google Drive permission, "drive", as Google didn't want us to use it. They instead suggested us to just use drive.file. The difference here is that the latter requires that the file was edited/added by Buttercup.

from buttercup-desktop.

Failed registering protocol: buttercup

This is usually due to missing/misconfigured components on the host system regarding custom protocols.

Should I create a new issue ?

Sure, you should feel free to - but it would probably only help if there was some easy way to reproduce it.

Edit2: After researches it exports OTP but into a field otpauth://totp/xxxxxx (no longer visible as a code)

Exporting to CSV doesn't preserve field types. It would be better for us to work on a Buttercup specific import/export format (we plan to do this, but have no issue yet) so that these are preserved.

from buttercup-desktop.

Getting back to the parent issue then - I think this comes down to adapting to the new way of working with Google Drive, without the open permissions option. I think we need an upload button in the file view, so we can upload local vaults to GDrive using Buttercup so they're accessible. That, or implement Google's own JS based file picker.

Sigh.. Google wastes so much of my time with this stuff.

from buttercup-desktop.

I can confirm that, I had the same problem with my windows computer and I found a workaround :

• download the "old" file and open it in local with bcup by creating a new vault.
• export it in csv buttercup file
• create a new empty vault on drive
• import the local csv file
  The new bcup file is now visible in the list when adding a new one.

But on linux (Ubuntu 20.04.6 LTS) I am stuck after google authentication, the magnet link is not opening & the desktop app still asking for login. (tried 3 browsers) The only error in terminal after init is : Failed registering protocol: buttercup Should I create a new issue ?

Thx

Edit: I just figured out that this does not export OTP codes, I there a way to do that ? Edit2: After researches it exports OTP but into a field otpauth://totp/xxxxxx (no longer visible as a code)

I had the same issue with buttercup protocol, I used AppImageLauncher to launch the application, everything went smoothly afterwards.

And also did the same solution you've mentioned. downloaded the old file, add it as a local resource. updated to version 2, exported the entries as CSV, created a new file on Google Drive then imported the CSV.

A long process but it worked

from buttercup-desktop.

Will close this issue to give way to other inquiries.

from buttercup-desktop.