Problem with own google drive client_id

I have a problem with my google drive client_id. I created one and entered it with rclone config, refreshed the app token, but it doesn't work. When I try rclone lsd gdrive: it doesn't return anything. Also in lights of recent google drive problems I've changed the user-agent using an environment variable. With verbose output it looks like this:

$ rclone -v -v lsd gdrive:
2019/05/16 13:28:21 DEBUG : rclone: Version "v1.47.0" starting with parameters ["rclone" "-v" "-v" "lsd" "gdrive:"]
2019/05/16 13:28:21 DEBUG : Using config file from "C:\\Users\\Zottelchen\\.config\\rclone\\rclone.conf"
2019/05/16 13:28:22 DEBUG : 4 go routines active
2019/05/16 13:28:22 DEBUG : rclone: Version "v1.47.0" finishing with parameters ["rclone" "-v" "-v" "lsd" "gdrive:"]

What is wrong? There are no errors or anything.
Normal rclone configuration works properly, though it needs to retry sometimes.

That seems to connect and work ok without a problem. Are you able to see if there are files on the other side? Did it work before?

I realised my mistake. I reauthenticated with the wrong account and that is probably why nothing was shown because on the other account the root-folder doesn't exist. 10/10 me. Sorry.

Yeah there are files, it is a restic repository. If I use the default client_id it works.

rclone lsd gdrive-bak:
      -1 2018-05-26 15:19:18        -1 data
      -1 2018-05-26 15:34:47        -1 index
      -1 2018-05-26 15:04:41        -1 keys
      -1 2018-05-26 15:19:14        -1 locks
      -1 2018-06-18 21:45:56        -1 snapshots

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.