View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017711 | MMW 5 | Sync | public | 2021-03-31 17:46 | 2022-09-14 14:39 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.2 | Fixed in Version | 5.0.1 | ||
| Summary | 0017711: MM5 is creating duplicate folder in Google Drive (when the folder is pre-created by user) | ||||
| Description | 1) Set up MM5 to sync to Google Drive with default mask (to sync to 'Music' folder) 2) Create the 'Music' folder manually in the 'Disk Google' web client 3) Sync some tracks using MM5 => MM5 creates duplicate 'Music' folder and sync the tracks to this duplicated folder https://www.mediamonkey.com/forum/viewtopic.php?p=479910#p479910 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2332 | ||||
|
|
Investigating this issue and found it that it is because of scopes that we are using. Currently we use only https://www.googleapis.com/auth/drive.file scope, which means that MM5 can create/delete/list only content created by 'MM app'. We would need to add at least https://www.googleapis.com/auth/drive scope. I am sure that previously we did not need further scopes to get the access and metadata -- e.g. accessing user photo to read was possible, but now it requires additional scopes like: https://www.googleapis.com/auth/drive.photos.readonly https://www.googleapis.com/auth/drive.readonly https://www.googleapis.com/auth/drive.metadata The problem is that upon adding the additional scopes it shows ugly waring that our app is not verified by Google and does not recommend to approve it when signing using OAuth2, more about scopes: https://developers.google.com/identity/protocols/oauth2/scopes |
|
|
It seems that adding https://www.googleapis.com/auth/drive.readonly works to resolve this issue and does not require the app to be verified by Google So used this in 2332. Test notes: User needs to 'Sign out' -> 'Sign in' again in MM5 to take the effect. Or alternatively create new 'Google Drive' profile. I also added user photo like this: https://www.dropbox.com/s/mjknyn9hsww40rg/Screenshot%202021-03-31%2021.23.41.png?dl=0 |
|
|
Verified 2332 Unable to replicate after 'Sign out' -> 'Sign in' to Drive account. Scheduled for closing after user confirmation. |
|
|
Re verified 2333 No more issues and regressions |
|
|
Temporary reverted the fix until Google give us approval of our verification process request, details in 0017960:0063697 |
