Need need bug verification - rclone about doesn't work on teamdrives (empty output)

What is your rclone version (output from rclone version)

rclone v1.50.2

  • os/arch: windows/amd64
  • go version: go1.13.4

Hey all,
I don't think rclone about has ever worked for me on teamdrives since as far back as 1.47 and earlier.
Before I create an issue on it, it would be helpful if a few people can check that they experience the same problem.

The check is of course super easy to do:

  • Have a Google Teamdrive configured
  • Run rclone about MyTeamdriveRemote:
  • Note if the output is empty or not (normally you should get statistics about the data)

It works fine on normal Google Drives. This is only regarding teamdrives (or "shared drives") as Google now calls them.

Yep, I can vouch for this. From my testing, it doesn't even send a HTTP request so this is probably disabled somewhere in the code itself.

It may be that it's not possible for teamdrives or something - but if that is the case I think rclone should spit out an error rather than a very confusing blank.

Hopefully it is possible though, because it contains a lot of useful info.

Last time I looked I couldn't find an API to read size info about a shared drive.

If it was anywhere it would be here I think:

However that returns something with no quota info:

Rclone calls the about call to for non team drives: which returns this: which has a nice storageQuota section, but I think that is only for the users drive

I'm happy to add it if we can dig up the API!

That is probably because there is no storage quota for Shared Drives. They have unlimited storage quota but only 400k total files+folders. I think we can still add the existing capability and probably create a bug for Google to fix if they want.

This will also solve the permissions issue since this is an easy check to do. However, it returns 404 (drive not found) instead of 403.

I'm not following here? Do you mean call the drives/get API?

Yes, exactly. That should solve the permissions error and return whatever details google provides for the drive, which, admittedly, is not much.

I've attempted to fix this here (uploaded in 15-30 mins)

This change:
- calls teamdrives get on rclone about
- calls teamdrives get on a listing of the root which returned no entries

These will both detect a team drive which has the incorrect auth and
workaround the issue.

I've merged this to master now which means it will be in the latest beta in 15-30 mins and released in v1.51

1 Like

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