View Issue Details

IDProjectCategoryView StatusLast Update
0011388MMASynchronizationpublic2013-11-08 16:57
Reporterrusty Assigned To 
PriorityimmediateSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.0.4 
Target Version1.0.4Fixed in Version1.0.4 
Summary0011388: Continuous prompts to update playlists on the server
DescriptionWhen creating a playlist on MMA, and syncing (with bidi sync enabled), then on subsequent sync operations, the user is prompted to update the playlists on the server.

I can't find any pattern to this, but this occurs often and repeatedly. e.g.

1 Create playlistA on MMA
2 Auto-sync
--> User is prompted to sync playlistA, and it's synced to MMW
3 Create playlistB on MMA
4 Auto-sync
--> User is prompted to sync both playlistA and playlistB!

Note: this occurs when no changes have been made to the playlist
TagsNo tags attached.
Fixed in build180

Relationships

has duplicate 0011415 closedmarek Static Playlists synced via USB are always resynced as updates over wi-fi 
related to 0011440 closedmarek Corrupted playlist synchronization in some cases 

Activities

Ludek

2013-10-18 20:28

developer   ~0037960

Last edited: 2013-10-18 20:30

I cannot replicate and AFAIK the only problem could be in the timestamp, but MMW uses the same timestamp as MMA sends when uploading the new playlist, so unless the playlist content is changed in some way, there shouldn't be a problem.

marek

2013-10-21 07:53

developer   ~0037962

Ludek is right. The only issue can be that it was changed somehow. Probably MediaStore had newer timestamp. And therefore playlist in our DB was updated.

Could you please provide a log when you observe this issue again?

rusty

2013-10-24 22:40

administrator   ~0038042

Unable to replicate with MMA 176 / MMW 1668

rusty

2013-11-02 23:44

administrator   ~0038155

Last edited: 2013-11-03 00:07

Further testing with 179 reveals a usecase in which this always occurs (Steps 4-5), and another in which it doesn't (Steps 1-3):

    0 Enable deletion of tracks not on the sync list, and bidi sync.
1 Add AutoPlaylistA (randomized) and PlaylistA to the sync list in MMA
2 Wi-Fi auto-sync
--> Sync occurs as expected
3 Autosync again
--> Tracks from AutoPlaylistA are prompted for deletion and then replaced with a new set as expected
4 Add ArtistX>AlbumX to the sync list in MMA
 . IMPORTANT: if at this step the user selects an Artist, rather than a specific Album by the Artist, then the bug at step 5 will not occur!!
5 Auto-sync
--> Tracks from AutoPlaylistA are prompted for deletion, but PlaylistA is also prompted for an Update even though there's no change!

Debug log: VC4KEHTJVB

Ludek

2013-11-03 14:20

developer   ~0038157

Last edited: 2013-11-03 14:21

Marek, why MMA takes timestamp from MediaStore? I think that the timestamp should be changed only when user edits the playlist directly in MM, isn't it?

I can also replicate, details here: 0011440:0038149

marek

2013-11-06 13:57

developer   ~0038199

Last edited: 2013-11-06 13:58

Fixed in build 180

Timestamp should be changed when user changes playlist in other app (in Mediastore) too. This playlist is synced to MMA.

I have fixed this issue only partly for some devices. MediaStore takes modified date from file's timestamp. So MMA is now changing the m3u file timestamp. BUT some devices and APIs (e.g. Nexus 7) doesn't allow to change file's modified time!! This is an android bug reported here https://code.google.com/p/android/issues/detail?id=18624 . So it is impossible to change modified date in Mediastore for such devices. Playlists have to be compared by items. This slows down the sync little bit.

rusty

2013-11-08 07:39

administrator   ~0038232

Verified 181 (tested Xperia Pro running ICS).

Leaving 'resolved' to confirm the ramification of 'partial fix'.

rusty

2013-11-08 16:57

administrator   ~0038245

The fix is comprehensive--just a bit slower on devices such as the Nexus 7 / Nexus 5 which don't allow MMA to update the .m3u file's timestamp.

Tested as well on a Nexus 5 running kitkat.