gobenoit06
commented
5 months ago Hey Mister Keeanywhere, any news about this MAJOR PROBLEM ? this prevents to use your plugin, please do something asap otherwise I can tell you that your plugin is dead !!! wake up, now
Kyrodan
It looks like there may be an issue with KeeAnywhere's App Verification status. The error screen that @ElizaZadura and I encountered in #393 is almost identical to this one that Google says you get if an unverified app exceeds 100 users.
Plus, I had no problem re-authorizing an account I had already added, nor even removing and re-adding the account. But as soon as I deleted KeeAnywhere from my Google Security dashboard I suddenly began having the same problem.
Googling the error message led to this article, which supports the idea that the App is missing a verification.
This Google support page also supports the idea that KeeAnywhere would require verification:
More info here also: https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes
Unfortunately, we use
drive(as discussed in #398 ), which is one of those restricted scope. https://github.com/Kyrodan/KeeAnywhere/blob/ebeb344177353ad663e1d0270920f7ca057b737c/KeeAnywhere/StorageProviders/GoogleDrive/GoogleDriveHelper.cs#L39 The official list of restricted scopes was not easy to find. I never did find the sensitive list.I don't remember seeing this screen in the past, which makes me think this app was verified in the past and has somehow lost that status?
Compiling my own copy, with my own test client_id and client_secret (and no other changes) made it so I did not get this issue. It's also possible that the change suggested in #398, switching the scope to
drive.filesmight help. Even though - as I said in the other issue - I prefer usingdrive, I admit thatdrive.fileshas a chance of working, because it is not in the restricted scopes list, and Google seems to take those extremely seriously.