View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013525 | MMA | DB | public | 2016-09-16 19:02 | 2017-02-22 16:13 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.2.0 | ||||
| Target Version | 1.3.0 | Fixed in Version | 1.3.0 | ||
| Summary | 0013525: All data lost upon running MMA Beta | ||||
| Description | I just ran MMA (after not having used it for a couple of days). When I ran it, content initially appeared and then after half a second, it was all deleted! i.e. MMA now shows 0 tracks on the device even though the files physically appear on the device. Log ID: R8YLIFY1Z1 DB: uploaded to the ftp server Note: - The three playlists that had been synced still show up (though all three are empty) - Content still appears within Google Play Music (or other android apps) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 669 | ||||
|
|
Additional possible clue: upon attempting to sync MMA, a new profile was generated in MMW! |
|
|
I can't replicate, but this looks like SDCard failed for a moment. |
|
|
The only solution seemed to be to reconfigure the new profile that had been generated with my old settings, and then resync. |
|
|
Unfortunately, I do not see the cause in the log. But it is most probably caused by the same issue that was fixed as part of 0013246 |
|
|
Reopen see 0013246 |
|
|
Another report: http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=86631 |
|
|
This is fixed as 0013246 in 1.3.0 |
|
|
Verified 657 |
|
|
I experienced this again with MMA 1.3.0 (unfortunately I didn't generate a log). I think that the trigger was that I'd Wi-Fi synced and lost the Wi-Fi connection. Sometime later when I ran MM, the library was empty. Tested on a Nexus 5x running Android 7.1. |
|
|
Still can't replicate. Steps I used: 1. Do a WiFi Sync (Aprox 100 Tracks) 2. Play number of tracks so that MMW gets updated Counters 3. Start another sync (added to profile another few hundred tracks) 4. Tried to turn off router/WiFi on device/Move out of range 5. Sync Cancels but original tracks and tracks that were synced are in library 6. Tried to Reconnect in Timeout period and all tracks gets synced 7. tried to Cancel sync to while connection is lost and also to regain connection while MMA show canceling 8. Even tried to Delete tracks that are not yet sync and not synced dialog showed correctly 9. Tried to be on reception/signal end to simulate timeout All MMA and MMW behavior was as expected |
|
|
Re-resolving as fixed. Marek indicated that in order to fix any residual issues, a log has to be sent immediately after the library is lost. |
|
|
Verified 667 Not seeing this in few past versions. |
|
|
Verified 667 during tests in 0013246:0047106 |
|
|
Can you confirm this? |
|
|
As I'd indicated I've been unable to replicate this. I'll reverify with 668 once it's ready. |
|
|
Tested with build 668 and this bug occurred upon running 668. Debug log: QQGJ4SB898 Tested as follows: 1 Clean install of 1.2.624 2 Sync playlist 'new download' and 'Shlomo Katz' after checking off auto-conversion for tracks > 192 kbps --> Tracks/Playlists sync and work as expected 3 Install 1.3.0.668 4 Click 'Tracks' --> No tracks appear 5 Click 'Playlists' --> 2 Playlists appear, but both are empty Note: an examination of /Music shows that the tracks do in fact exist 6 Click 'Sync' --> Sync proceeds as if no tracks are on the device (i.e. all 34 tracks resync) |
|
|
Fixed in build 669 It was caused by following situation: 1. Install MMA 1.2.0 2. Go to Library Folders and remove /Music folder 3. Go to sync settings in MMA (/Music folder will be automatically re-added) 4. Update to MMA 1.3.0 5. Sometimes /Music sync folder was not correctly migrated from 1.2.0 to 1.3.0 and was removed from Library - including all tracks That is the usecase that should be tested mainly. But a refactor was needed so other parts of Library folders management should be tested too. |
|
|
Verified 670 I've tested on three devices 4.1.2, 4.2.2, 5.1 with no regressions |
|
|
Verified 670 on Android 7, and the issue seems to be resolved, however, there's a regression in 0013957 re. playlist matching. Leaving this as 'resolved' since we'll need to retest once 0013957 is resolved. |
|
|
Verified 671. |
