OOB OAuth deprecation: migrate to OAuth loopback mechanism

[bsidhom]

The Out-of-Band workflow will be deprecated in October 2022. As far as I can tell, drive still uses OOB (copy/paste) to authenticate.

I think that existing (authenticated) clients will continue to work at this point, but I'm not sure how long new authentication flows will continue to work. Desktop applications should migrate to a loopback device flow.

[tom-ch1]

Checkout how Brian adapted grive2 to migrate oob to loopback flow: vitalif/grive2#369
Maybe the same approach works here

[jeffman]

When I visit the link produced by drive init ~/gdrive, I get:

Access blocked: drive for Google Drive’s request is invalid

You can’t sign in because drive for Google Drive sent an invalid request. You can try again later, or contact the [developer](https://accounts.google.com/) about this issue. [Learn more about this error](https://support.google.com/accounts/answer/12379384)
If you are a developer of drive for Google Drive, see [error details](https://accounts.google.com/).
Error 400: invalid_request

Is the error I'm seeing due to this issue?

[indev29]

Is the error I'm seeing due to this issue?

Unfortunately, yes. You can try a fix from #1142 for now.
I'm not sure when it will be merged to master, seems like the project is not actively maintained at the moment.

[grovera-md]

Is there any update on this issue? Installing the @latest version still produces the error.

[bsidhom]

The fix from #1142 hasn't been merged yet, so it won't appear in @latest. I'm not sure if this repo is still maintained, but for now, you'll have to patch in that change and build locally if you want the fix.