View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016125 | MMW 5 | Sync | public | 2019-11-19 16:35 | 2019-12-11 14:10 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0016125: Duplicate device profile can be created when the device is in unreadable state | ||||
| Description | There seems to be a way how to get device to the unreadable state and making MM5 to create duplicate device profile. Barry has found these steps: The sequence that seemed to cause the duplication was: * phone connected via USB ... MM device for the phone is in status of "connected" * "scan as soon as device is connected" is checked ... also "grant remote sync" * on the phone: toggle USB Preferences from "File Transfer/Android Auto" to "No Data Transfer" * toggle back to "File Transfer/Android Auto" This step does the trick: * on the phone: toggle USB Preferences from "File Transfer/Android Auto" to "No Data Transfer" In that case the MM5 fails to read the storageInfo.xml file from the device and thus fails to read the profile key and creates the new profile (for this "unreadable" storage) | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=95379#p463065 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2214 | ||||
|
|
The strange is that we have already a mechanism for this from the past, see 0013283 So to be found why the dialog does not popped up in this case too. |
|
|
Fixed in 2214. i.e. the message dialog from 0013283 is used and the duplicate profile isn't created. |
|
|
Verified 2214 No duplicate profiles created and dialog shows correctly |
