User disconnecting app in Drive causes loss of data under FILE scope

Question

I\'ve run into this issue a few times, but could never point my finger on it, attributing it to GDAA\'s latency, my buggy code, etc... I finally managed to come up with a s

Answer 1

The first issue is:

1. A user revokes authorization via: Settings > Manage Apps > Disconnect From Drive
2. Then reauthorizes that App
3. Files this App was authorized to see with DRIVE_FILE scope are no longer authorized.

This is the expected behavior of the REST and Android APIs.

We don't think users would intuitively expect all previously authorized files to be re-authorized. The user may not remember the files that were previously authorized, and informing users that these files are going to be authorized again will likely cause confusion.

The second issue is GDAA's behavior for folder creation in this situation. We don't currently support CompletionEvents for folder creations, but this is something we'll look into.