Cannot get OAuth

[jtgd]

$ skicka ls
skicka: error creating Google Drive client: Get https://www.googleapis.com/drive/v2/about?alt=json: oauth2: cannot fetch token: 400 Bad Request
Response: {
  "error": "invalid_grant",
  "error_description": "Bad Request"
}

$ skicka -no-browser-auth ls
skicka: error creating Google Drive client: Get https://www.googleapis.com/drive/v2/about?alt=json: oauth2: cannot fetch token: 400 Bad Request
Response: {
  "error": "invalid_grant",
  "error_description": "Bad Request"
}

Nothing opens in browser.

Is there a workaround?

(Arch Linux aur/skicka r272.70827bf-1)

[ardunn]

I am having same issue

[ClaraBing]

I'm having the same issue too; it used to work before but gave this error today.

Update: I removed the cache files (~/.skicka*cache*) to sign in to my account again, and got this error message:

"Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In."

Looks like skicka is now disabled?

[satackey]

I have successfully logged in with an account that has used skicka.
However, for new accounts that sign in to skicka, I received the error message "Sign in with Google temporarily disabled ...".

I think the cause is that the default credentials embedded in skicka have not passed Google's review.
This was solved by creating your own credentials.

Here are the steps:

1. Create a project on Google Cloud Plarform.
2. Select API & Services-> Library in the menu and enable Google Drive API.
3. Select Create OAuth client ID and get Client ID and Client Secret.
4. Comment out and rewrite clientid and clientsecret in the [google] section of .skicka.config.

[mxdpeep]

abandon skicka, use rclone

[jtgd]

Heh, thanks. Already did.

[agoode]

This is still a problem. I think the instructions here are still relevant:
https://github.com/google/skicka/blob/9c807e9f5e3e66e9fa588511f058628ea5db89be/README.md

Please leave this issue open so people can find this workaround.

[lukewys]

Hi, @satackey , I wrote the clientid and clientsecret according to your instruction, but afterwards when I run skicka ls it still let me get the authorization. Is there anything that needs to perform after changing the config file? Thanks in advance.

[lukewys]

Hi, @satackey , I wrote the clientid and clientsecret according to your instruction, but afterwards when I run skicka ls it still let me get the authorization. Is there anything that needs to perform after changing the config file? Thanks in advance.

I succeeded. I clicked advance option in the link provided by skicka ls -no-browser-auth, and get the code.