buttercup / buttercup-browser-extension

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

OAuth callback doesnt propagate back to app in ubuntu #339

Closed midgethoen closed 4 years ago

midgethoen commented 4 years ago

I've been using the buttercup extension for a while now and i like it

however i cant get the desktop app to connect to my google drive archive, because the oauth callback does not automatically open the app and i dont know how to do this manually.

image

than nothing happens

additionally, in case it might be related, i get an error when starting the app or when checking for updates .

image

i'm on ubuntu 19 and unfortunately I`m not really equipped to troubleshoot this. if anyone can point me in the right direction that would be very much appreciated.

midgethoen commented 4 years ago

Allright i did some digging and fount the problem.

journalctl --user -f -g buttercup
-- Logs begin at Sun 2020-03-29 09:17:16 CEST. --
mei 07 11:18:07 ubuntu-workstation buttercup-desktop.desktop[2406]: 11:18:07.243 › Error: Error: ENOENT: no such file or directory, open '/opt/Buttercup/resources/app-update.yml'
mei 07 11:18:07 ubuntu-workstation buttercup-desktop.desktop[2406]: [Error: ENOENT: no such file or directory, open '/opt/Buttercup/resources/app-update.yml'] {
mei 07 11:18:07 ubuntu-workstation buttercup-desktop.desktop[2406]:   path: '/opt/Buttercup/resources/app-update.yml'
mei 07 11:18:18 ubuntu-workstation chromium_chromium.desktop[2406]: user-open error: Supplied URL scheme "buttercup" is not allowed

The browser being used for the oauth dance (chromium) was installed using the snap store, which apparently restricts the allowed url schemes which can be opened from this applications and buttercup:// is not one them...

I switch the default browser to chrome installed via apt and it worked like a charm.

Turns out this has nothing to do with buttercup...