search

buttercup / buttercup-browser-extension

:earth_asia: Buttercup browser extension
https://buttercup.pw
MIT License
228 stars 42 forks source link

Failed unlocking source: Failed fetching Google Drive vault: n.refreshToken is not a function #366

Closed llcoolju closed 3 years ago

llcoolju commented 3 years ago

Since the 2.21.0 update I get this error message when I try to unlock every single vault hosted on Google Drive :

Failed unlocking archive Unable to unlock archive (xxxxx): Unlocking archive source (xxxxx) failed: Failed unlocking source: Failed fetching Google Drive vault: n.refreshToken is not a function

Browser : Chromium OS : MacOS

lucasburlingham commented 3 years ago

I have the same problem on Google Chrome, and this problem has only been around since the latest update (2.21.0 - 08/31/2020)

Specs:

5.0.4183.83 (Official Build) (64-bit) Revision | 94abc2237ae0c9a4cb5f035431c8adfb94324633-refs/branch-heads/4183@{#1658} OS | Linux (Ubuntu 20.04 running GNOME 3.36) JavaScript | V8 8.5.210.20

AND

Google Chrome | 84.0.4147.135 (Official Build) (64-bit) (cohort: Stable) Revision | c42bd09b3f24da1698d71d3b4f57402137163566-refs/branch-heads/4147@{#1102} OS | Windows 10 OS Version 2004 (Build 19041.450) JavaScript | V8 8.4.371.23

I have tried to resolve this issue by removing the archive and then adding it again with the same details. image

I have noticed that there is not an issue on the Buttercup Desktop version (Again, I am running Ubuntu 20.04, see neofetch output: image.

anataty commented 3 years ago

Hi, got this problem since 2.21.0 version. Browser: Mozilla Firefox for Manjaro, Version 79.0 (64-bit) OS: Manjaro Linux, 64-bit, GNOME version 3.36.5

Gkupce commented 3 years ago

I too am having this problem, for now I found that removing the vault from the chrome extension, and re-adding it serves as a workaround, but it is definitely not ideal.

Browser version: Google Chrome 85.0.4183.83 (Official Build) (64-bit) OS: Windows 10 up to date (1st September 2020)

rafaelsza commented 3 years ago

I'm also having the problem, using Google Chrome on Windows 10 PRO 64-bits, I can only access it if I remove the safe and add it again, it seems to be a problem with one of the extension's methods.

perry-mitchell commented 3 years ago

Most likely an API change here: https://github.com/buttercup/buttercup-browser-extension/blob/4a07ebe250bcc02586312b798f3f44a517175d65/source/background/library/googleDrive.js#L67

Whereas in the latest Google Drive client it's: https://github.com/buttercup/google-oauth2-client/blob/master/source/OAuth2Client.js#L79

I'd thought that our client had always been similar in terms of API with regards to the original Google OAuth2 client, but seems not. This should be an easy fix - Happy to accept a PR or I can look at it later today.

iconhouse commented 3 years ago

Any updates on when it might be fixed? It updated again today but I can't use it with a failed fetch google drive error. I tried rafaelsza method but restarting browser resets error again. Now I am using desktop version. BTW, thank you for having desktop version.

denali1 commented 3 years ago

This also occurs on Microsoft Edge Chromium Dev.

Microsoft Edge is up to date. Version 86.0.622.3 (Official build) dev (64-bit)

perry-mitchell commented 3 years ago

Fixed - I'll release this very shortly (this evening).

EDIT: Live soon as v2.23.0

carboncls commented 2 years ago

I just encountered this issue again. Browser: Brave MacOS

Failed unlocking archive Unable to unlock archive: Unlocking archive source (3caf1a07-6f45-4ebc-8372-a51ebc2f8cff) failed: Failed unlocking source: Failed fetching Google Drive vault: Request failed: 400

caverna commented 1 year ago

and now for a couple days again... :-(

rafciozarzecz commented 1 year ago

and now for a couple days again... :-(

I logged out from all google accounts in the default browser and it helps, but I'm not sure for how long...

abashtovyigeniusee commented 1 year ago

I experience the same issue these couple of days