View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019358 | MMA | Synchronization | public | 2022-09-08 02:14 | 2022-12-19 19:08 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 2.0.0 | ||||
| Target Version | 2.0.1 | ||||
| Summary | 0019358: Bi-di sync of playlists results in conflicting behavior (deletion and subsequent resync) | ||||
| Description | In cases where MMA is configured to sync content from the device to the server, MMA prompts the user to: Upload the playlist (enabled by default) Delete the playlist (disabled by default) When a playlist is uploaded, it is also automatically added to the auto-sync list (so that it won't be deleted). BUT if the user enables Deletion of the playlist, then the playlist is deleted from the device on sync, and will then be resynced to the device on the next sync operation (because it's been added to the auto-sync list)! Would it make more sense for the user to only be able to confirm Upload OR Delete (rather than both)? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Are you sure that the playlist is deleted? I would expect that uploading it from MMA to MM5 causes the playlist to be added to sync-list and thus NOT subsequently deleted? AFAIR this is how it always worked with MMA 1.X Anyhow allowing either to upload or delete makes senso IMO |
|
|
Yes. The confirmation dialog for the playlist shows both an upload icon and a delete icon. And when both are enabled, the described workflow is what resulted. |
