So I started a sync with google drive and set it to drive.file scope. As client_id/secret weren’t needed, I left them blank. Upon further research and log files filled with rate limits from the global client_id, I made my own. Sync continued happily, realizing there were existing files.
Later on I decided to delete some files and move things around with rclone move and get these messages on some files:
2018/09/04 22:26:23 ERROR : Attempt 3/3 failed with 1 errors and: googleapi: Error 403: The user may not have granted the app #### write access to all of the children of file xxxx., appNotAuthorizedToChild
Eventually I found that if I go and remove my client_id/secret, I could move those files just fine.
In other cases I found that if I copy a file without client_id, I couldn’t see it with client_id set. So I’m not quite sure how this all works - my rclone sync when I changed my client_id appeared to see files that were unchanged (I run with verbosity set to DEBUG), but I’m not positive anymore. One of the folders I did a
Nevertheless, is there any way to convert access on these older files so my client_id can have full permissions on them?
Or is everything completely invisible for one client_id to the other with drive.file scope set? If so, can I do a full rclone purge on the blank/global client_id and not affect my personal client_id (which now is fully sync’d) when the folder names are the same? If this is the case, how does the write access error occur?
Also, if this was the case, wouldn’t my personal client_id see its own folder with the name I’m referring to, and have full write access to everything underneath? Why does that error even come up then? It shouldn’t be able to see the global client_id’s folder under that namespace.
I’d recommend some notes about this be added to the client_id/scopes section.