Implement Google Picker API

[mifi]

Problem

Google Drive scope drive.readonly which we currently use has become restricted, meaning google requires strict validation in order to use this scope. This includes security assessments from a third-party companies.

It's clear that Google wants to push vendors over to the Picker API instead.

Solution

Use the recommended/non-sensitive drive.file scope instead. The problem is that this scope requires us to use a completely different API, as well as Google's UI to pick files.

drive.file: Create new Drive files, or modify existing files, that you open with an app or that the user shares with an app while using the Google Picker API or the app's file picker.

Alternatives

Not that I know of, other than dropping Drive support or keeping the existing implementation

References

• All Google OAuth2 scopes
• Google Drive scopes showing which are restricted
• Google Photos scopes
• Official Picker sample code
• https://developers.google.com/drive/picker/guides/overview
• Google Drive Permissions/Scope Update #4793 (comment)

Discussion

There's some old code that seems to support Google Picker with Photos, but the demo app is blocked by google.

Note that Google Photos scope https://www.googleapis.com/auth/photoslibrary.readonly is restricted and also requires verification. There doesn't seem to be any way of getting Google Photos in the Google Picker API.

• https://stackoverflow.com/questions/78812117/trying-to-implement-google-photos-picker-api
• https://stackoverflow.com/questions/55326819/can-you-use-the-google-photo-api-with-the-google-picker
• https://stackoverflow.com/questions/76680469/how-to-make-photo-picker-show-images-from-google-photos
• https://stackoverflow.com/questions/57861974/is-there-a-way-to-select-google-photos-that-are-not-in-an-album-using-the-google