Does the FNC Cloud Pack library influence the "scope" rules of Google Drive?

[Leahy_Michael]

I've created an Android app using FNC Cloud Pack to access Google Drive.

The app, "verified" by Google, has just one Google "scope" which is to "See, edit, create and delete only the specific Google Drive files you use with this app."

When the app runs on a new Android device, it is stopped by the screen that says it is not verified. When I click the Advanced link and tell it to proceed anyway, it shows me two scopes that I can choose with two checkboxes. The second one is the expected scope mentioned above. The first scope shown however is,

"See, edit, delete and create all of your Google Drive files."

If I select only the second scope (giving permission to the app to access only files used by the app) then everything works as expected. The app creates its own folder and successfully uploads and downloads files there.

Is there something the TMS FNC library is doing which makes Android/Google think it wants to access files beyond this scope?

[Pieter_Scheldeman (Pieter)]

The scopes that are added to verify the application against the endpoint are

Scopes.Add('https://www.googleapis.com/auth/drive');
Scopes.Add('https://www.googleapis.com/auth/drive.file');
Scopes.Add('https://www.googleapis.com/auth/userinfo.profile');

You can manipulate the scopes by accessing them directly via TMSFNCCloudGoogleDrive1.Scopes before connecting to the service.

[Leahy_Michael]

I'm using the TMSFNCCloudStorageServices component. Do I need to use the Google Drive component to get access to the Scopes property?

If this is documented somewhere please let me know.

[Pieter_Scheldeman (Pieter)]

With the TMSFNCCloudStorageServices component you can access the storage & the scopes directly with

TMSFNCCloudStorageServices1.Storage.Scopes