|
|
bug17960.png (44,133 bytes) |
|
|
It seems that the warning is appearing because permission for read-only access to Google Drive was requested as part of the fix to 0017711 (allowing users to scan pre-existing media content on their Google Drive). MediaMonkey has been 'submitted for approval' re. the new set of permissions however, they've indicated that "The review process can take up to 4-6 weeks. Expect the first email from our Trust and Safety team within 3-5 days. Your last approved consent screen is still in use." Is it possible to limit the permissions requested by the app (e.g. for MM 5.0.1 only request permission to access content uploaded by MediaMonkey to prevent the warning, and in 5.0.2 include the fix to 0017711) so that only beta users would receive the warning (and would stop seeing it in 4-6 weeks when verification is completed)? |
|
|
OK, removed the drive.readonly scope (reverted fix of 0017711 and re-opened 0017711 to include the scope back once we have the Google's approval). Fixed in 2411 |
|
|
BTW: I guess we can live with the drive.file as the only scope atm We can see only content uploaded by MM, but at least the metadata will be there, so that's fine Just needs to be documented that the content needs to be uploaded by MM Seeing that it is already partially documented here: https://www.mediamonkey.com/wiki/index.php/WebHelp:Cloud_Services/5.0 Namely: "It's recommended to use MediaMonkey to upload files to the Cloud Service as MediaMonkey creates its own database with the media file's tags. This metadata will be missing if you upload files to the Cloud Service outside of MediaMonkey. You can select what content from the MediaMonkey Library and set how this content is synced to the Cloud Service:" So we should probably adjust this text for Google Drive (that does not see third party content at all atm) and make this text bold? |
|
|
Verified and documented on 2411 |
- Anonymous
