View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011483 | MMA | Synchronization | public | 2013-11-15 17:40 | 2013-11-16 02:15 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | block | Reproducibility | sometimes |
Status | closed | Resolution | fixed | ||
Product Version | 1.0.4 | ||||
Target Version | 1.0.4 | ||||
Summary | 0011483: Synchronization fails (regression 184) | ||||
Description | With build 184, synchronization fails in some cases, though it succeeds in others. When it fails: - debug logs are sent as tracks begin to be copied (while the sync operation continues) - at the end of the sync operation the following error occurs: Completed with errors --------------------- Failed storings (9) | ||||
Steps To Reproduce | I experienced the bug at 12:30 EST on an Experia pro. Logs automatically sent. Peke also experienced the bug and along auto sent syncs he sent two manual from Nexus 7: LGY2GSZBWE - During Sync 90CAD6EXZI - After Sync Ended with "Failed Storings (387)" | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in build | 185 | ||||
|
Further testing shows that: Sync succeeds whenever the operation only involves modifications to playlists. Sync fails whenever the operation involved tracks being copied to the device. When tracks are copied to the device, the debug log is triggered and the sync eventually fails; tracks appear to be copied to the device (both unconverted and auto-converted tracks), but at the end, an error shows that they all failed. An examination of the device confirms that the tracks failed to copy. |
|
Fixed in build 185. |
|
Verified 185 |