View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016112 | MMW 5 | Sync | public | 2019-11-12 22:50 | 2019-11-14 22:02 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0016112: Synch tree fails to update and crashes | ||||
| Description | In build 2211, I'm experiencing a couple of possibly related issues: 1) When a podcast is selected in the MM5 sync list, it doesn't show up as selected in the corresponding MMA Sync list (possibly related to 0015985) ? 2) If the user tries to deselect 'Music' on the device --> nothing happens (the user is only able to deselect 'Album' or the AlbumName). 3) BUT, unchecking Album on the device --> Crash in MM5: CrashlogID A04C23C6 (this isn't on the video as it didn't occur on this occasion) 4) Rechecking the Top Gun album on the device --> Crash in MM5: CrashlogID A04CE0BE 5) for steps 2/3/4 every time the user makes a change in MMA, the user is prompted to accept the changes in MM5 (if the device is open). I'm not sure if this is a great idea because it could result in situations in which the remote user believes that changes to the sync list have been made, when in actuality they haven't because the desktop user hasn't accepted them. I don't remember observing this behaviour in the past. https://www.screencast.com/t/WnP5vKyg4Yly | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 2212 | ||||
|
|
1) is fixed in 2212. Test note: the podcast added by previous build needs to be deselected+selected again and the [Apply] button needs to be clicked for this visual issue to take effect 2) This works same in MM5 and in MM4 (and has always worked like this in MMA too), i.e. deselecting all music changes it back to the partly checked state (with previously selected music content) 3,4) are fixed in 2212 (together with some further issues that I have found during testing) 5) Was a regression introduced and already fixed during 0016078 |
|
|
Verified 2212 (though in the course of testing, figured out how to replicate 0015985 issue 1). |
