Cyberduck installed from Microsoft Store fails oauth process for googledrive authentication.
During the app waiting for the browser response about user authentication/authorization, the browser doesn't kick back to the app.
The authorization page is redirected to the google top page without displaying any dialogs.
I tried several times to reproduce this issue with the app installed from the Microsoft Store and the app from the web installer, and found that: if I installed it from the web installer, the following registry keys are created, but if I installed from the Microsoft Store, it isn't.
I guess this registry key is necessary to work oauth properly.
This registry key is specified as oauth redirect url in the commit 9626cfc .
So, I tried to avoid this issue by creating such registry keys manually, and confirmed it works fine.
One thing I have to be careful is the installation path, there is a difference between the app installed from the Microsoft Store and from the installer.
Install the cyberduck from Microsoft Store and try to connect to googledrive.
Note: If you have already installed the installer version previously, registry key may be remains. In that case, the browser try to open "custom handler" app in oauth process. But it won't work because the regisry key named "command" does not indicate the proper app path.
Oauth succeed and files in the googledrive listed.
Desktop (please complete the following information):
Windows 11 21H2 22000.856
Google Chrome 104.0.5112.102
The text was updated successfully, but these errors were encountered: