View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014311 | MMA | Synchronization | public | 2017-07-25 08:54 | 2017-08-30 10:59 |
Reporter | marek | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 1.3.1 | Fixed in Version | 1.3.1 | ||
Summary | 0014311: MMW inserts invalid album artwork value during USB sync | ||||
Description | I have added path verification to MMA so we can detect invalid paths in mmstore.db.synced. Now there are many occurences of crashlogs where path is '-'. This char is used as flag by MMA to mark that the album artwork was lost/deleted. It should be restored during next sync from MMW. Here I could see that media was updated with this flag by MMW. But it should be replaced by valid album art path or by null value. There are many occurences from different devices using these MMW builds 1813-1840 | ||||
Tags | No tags attached. | ||||
Fixed in build | 721 | ||||
|
I traversed the code carefully and verified that MMW couldn't write '-' to media.album_art at all. It always writes null or a value with (at least) image file extension (*.jpg, *.thm). The only idea I have is that DB triggers like insert_media_* would remain in the mmstore.db while processing by MMA and inserting a new track by MMA would cause the trigger call and thus writing to sync_operations table? |
|
Marek added more debug info to the next MMA build to find more... |
|
Triggers cannot cause it... mmstore.db (internal MMA DB) and mmstore.db.synced (from MMW) are two different DB files and these MMW triggers are never created in internal mmstore.db. Now I am sure that there is a update (not insert as mentioned in issue description) operation for album artwork value with '-' char as new value. In next build 719, mmstore.db.synced will be packed in crashlog so we can see all records in sync_operations table |
|
Fixed in build 721 |
|
Verified 724 along with ":" tests |