View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013881 | MMA | Synchronization | public | 2017-01-06 06:10 | 2017-01-27 14:19 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.3.0 | ||||
| Target Version | 1.3.0 | ||||
| Summary | 0013881: Anomalous behavior when installing MMA 1.2.0 and uninstalling MMA 1.3.0 | ||||
| Description | Over the course of testing build 660, I noticed some strange behavior in the following case: 1 installed MMA 1.2.0 and synced 2 uninstalled MMA 1.2.0 and installed MMA 1.3.0 and synced 3 uninstalled MMA 1.3.0 and then installed MMA 1.2.0 and synced --> sync errors / incomplete synchronization 4 delete tracks in MMA 1.2.0 --> they appear to delete, but they remain on the device I suppose that the DB from MMA 1.3.0, isn't backwards compatible with MMA 1.2.0 ? If so, would it make sense to version check that a DB is compatible? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
You are right, it isn't backward compatible. We convert all paths to document id form. And we do not have any code to convert it backwards of course in 1.2.0. What did you mean by adding version check? |
|
|
Per discussion: How about something like: 'The MediaMonkey database on your device is from version x.x and is not compatible with the MediaMonkey y.y. Delete the database and rescan? [Yes] [No] |
|
|
I have discussed this with Martin and he said that deletion of DB when downgrading is already implemented. And it works fine for me too. There is no dialog but it should be deleted. You have some issues after downgrading ? Could you please send log from 1.2.0? |
|
|
Waiting for build 665 to test due to 0013922 |
|
|
I can't replicate this in 665. Resolving. |
