View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0013963 | MMA | Synchronization | public | 2017-01-30 19:05 | 2017-01-31 00:52 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | major | Reproducibility | sometimes |
Status | closed | Resolution | fixed | ||
Product Version | 1.3.0 | ||||
Target Version | 1.3.0 | Fixed in Version | 1.3.0 | ||
Summary | 0013963: Some files/artwork are synced to primary:Music/ | ||||
Description | This issue was originally mentioned at 0013957 with repro steps in 0013957:0047112 . The issue is that in some cases: 1) content is synced to primary:Music/ instead of /Music/ 2) artwork is synced to primary:Music/ instead of /Music/ In addition: - content/artwork synced to that location isn't viewable within the MMA library (because it's not a scanned location) - content/artwork synced to that location isn't deleted during sync operations (probably because it's not part of the MMA library). The problem of content being synced there was last observed in builds from Dec. 26. The problem of artwork being synced there is observed with current builds 1.3.0.667 (though not with all tracks-- only for .../Say hi, .../Unknown, .../Various). | ||||
Tags | No tags attached. | ||||
Fixed in build | 668 | ||||
|
It was actually caused by the same issue as 0013957. But this should be managed by application and assert has to be thrown. So now this form of Document ID is not possible. I have added appropriate tests too. Fixed in build 668 |
|
Verified 668. |