Google blocking skicka token generation access. How Can I overcome this. People are suggesting to use rclone

$ skicka ls
skicka: attempting to launch browser to authorize.
(Re-run skicka with the -no-browser-auth option to authorize directly.)

problem

When I download a folder from google drive using this action, the file owner is root:root.

I am running a test program in CI, which place new files in a downloaded folder by this action.
However, when program try to place new files, I've got Permission Denied because the owner of the downloaded folder is root:root.

As a workaround, I have added a process to change the owner of the folder after downloading the folder by action.
An example is shown below.

name: Test
on: [push]

jobs:
  build:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        python-version: [3.9]
        os: [ubuntu-latest]

    steps:
      - uses: actions/checkout@v2

      - name: Download test data from Google Drive
        uses: satackey/action-google-drive@v1
        with:
          skicka-tokencache-json: ${{ secrets.SKICKA_TOKENCACHE_JSON }}
          download-from: /test-data
          download-to: ${{ github.workspace }}/tests/files/test-data/
          google-client-id: ${{ secrets.GOOGLE_CLIENT_ID }}
          google-client-secret: ${{ secrets.GOOGLE_CLIENT_SECRET }}

      - name: chown testdata dir (because satackey/action-google-drive@v1 downloads files as root owner)
        run: sudo chown -R runner:docker ${{ github.workspace }}/tests/files/test-data

suggestion

I would like to achieve simplicity in the description, preferably by specifying the user in the action.

For example, can we use the following option?

      - name: Download test data from Google Drive
        uses: satackey/action-google-drive@v1
        with:
          skicka-tokencache-json: ${{ secrets.SKICKA_TOKENCACHE_JSON }}
          download-from: /test-data
          download-to: ${{ github.workspace }}/tests/files/test-data/
          google-client-id: ${{ secrets.GOOGLE_CLIENT_ID }}
          google-client-secret: ${{ secrets.GOOGLE_CLIENT_SECRET }}
          user: runner # added
          group: docker # added

Hey, I've never used skicka before, and I'm following the steps described in the README. As per the troubleshooting procedure, after I get the "Sign in with Google temporarily disabled for this app" message, I'm trying to set up the Google Drive API client ID and secret, and set them in skicka.

I follow all the steps in the (translated) article. There is one difference, though:

when I'm asked for Application type, there is no "other" option, so I tried with Desktop app - the only one that does not ask for any additional info, apparently. After completing the steps though, after editing the .skicka_config and opening the URL that is given by skicka -no-browser-auth ls, I get the following error:

where I cancelled my gmail address.

Any ideas of what I might be missing?

The troubleshooting needs to be updated, I did everything as detailed in japanese, and got this:

It is one step further from the app being blocked, it still is not working as needed.

Perhaps that means skicka won't be supported in the long term.

It appears that the setup steps for generating a Skicka token no longer work as expected, as the client Oauth App has been deleted:

The Skicka repo has been archived, as noted in #21 so it appears the project has been fully sunsetted.

My workflow is that I want to edit content in Google Drive and that gets downloaded by the action and included in my build.

Specifically, I'm using Gatsby to generate static site content from markdown and I want to store the markdown in Google Drive and have it pulled automatically

I tried to setup skicka for the first time using the readme provided but ran into an error.

Github workflow is failed

This action require runner to ubuntu only but I have windows based artifacts

Hi satackey, thank you for this amazing tool!

I'm almost ready to use it, but I'm still missing something. I can see that download-to and upload-from are, by default, the current directory. But what do you mean by that? What is this current directory from where I'm meant to upload the files?

Thank you again for your help!

After "Updating metadata cache: 99.95% 12s" it says "skicka: IRL-L2-Support: not found"
I do not know what this means.

The workflow push-prebuild.yml is referencing action satackey/push-prebuilt-action using references v0.1. However this reference is missing the commit 0c027b66503f3857cb4e5cfb71633cc54dbd1ec6 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

https://accounts.google.com/o/oauth2/auth?client_id=********-**********.apps.googleusercontent.com&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&response_type=code&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive&state=********

This application is blocked This app tries to access sensitive information on your Google Account. To keep your account safe, Google blocks this access

Thanks for providing this action!
I have lots of files in my Drive, Updating metadata cache took me more than one hour.
Can I skip this step? Or is there a way to cache the metadata in GitHub Actions?

I tried to log in with my user and google threw an error saying sign-in has been disabled for this app.

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.

First of all I want to thank you because of a really good guide to configure and get the credentials, the other actions assume that everyone knows it

Every time I try to run this action, it returns this message:

2020/05/02 00:46:05 created configuration file /github/home/.skicka.config.
Go to the following link in your browser:
https://accounts.google.com/o/oauth2/auth?client_id=xxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&response_type=code&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive&state=

skicka: error with OAuth2 Authorization: oauth2: cannot fetch token: 400 Bad Request
Response: {
  "error": "invalid_request",
  "error_description": "Missing required parameter: code"
} 
Enter verification code: 

I followed the steps as it show in the guide, but it seems I had to verify again the login in the github action terminal

Currently, the directory of upload-to property need to be created manually before the action runs to avoid the following error:

skicka: /path/to/upload: not found

It would be really convenient to create the target directory before the upload.

skicka mkdir -p /path/to/upload

By doing so, this action can be easily integrated with variables with simple expression. For example,

- name: Upload files to Google Drive
  uses: satackey/action-google-drive@v1
  with:
    skicka-tokencache-json: ${{ secrets.SKICKA_TOKENCACHE_JSON }}
    google-client-id: ${{ secrets.SKICKA_GOOGLE_CLIENT_ID }}
    google-client-secret: ${{ secrets.SKICKA_GOOGLE_CLIENT_SECRET }}
    upload-from: ./app/build/outputs/apk/
    upload-to: /my-app/apk/${{ steps.extract_version.outputs.appVersionName }}/

The expression, ${{ steps.extract_version.outputs.appVersionName }}, might be changed every time the action runs.