View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013005 | MMW v4 | Synchronization | public | 2015-12-08 14:16 | 2016-02-10 11:32 |
| Reporter | peke | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1.10 | ||||
| Target Version | 4.1.10 | Fixed in Version | 4.1.10 | ||
| Summary | 0013005: MWM Create double Profile each MMW Start (when info file cannot be written) | ||||
| Description | Most likely due the bug 0012999 on Start MMW create new profile for Internal Storage. It happen to me few times, but it is not consistent. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1775 | ||||
|
|
Peke, I guess that they are created _everytime_ when you manually deleted storageInfo.xml, right? It is because 0012997:0043512 But it is all right, the reasons are that single SD card can be put to various Android devices or SD card slots and there isn't any other way how to pair a storage with a profile without this info file. |
|
|
I do not have issues with SD card but with Internal Storage where "files" is file not folder and MMW can't read StorageInfo.xml In 0012961 I always start with Clean MMW/MMA installs where there is no profiles at all so once storageinfo/xml is created which it can't be created due the 0012999 it should be read each time and not try to creat new one on each start. |
|
|
OK, so it is consequence of 0012999 where MMW cannot write the StorageInfo.xml.mmw because the 'files' is presented as file and not folder. The true is that the newly generated GUID shouldn't be assigned to a profile until the StorageInfo.xml.mmw is successfully uploaded. |
|
|
Fixed in 4.1.10.1775 |
|
|
My guess that StorageInfo.xml.mmw is updated by MMA but MWM can't read it so it create new one and loop is created. Will test in 1775 |
|
|
I had observed this in prior builds but not in 1775. Leaving for Peke to verify/close. |
|
|
verified 1776 Just to ensure bug was still present in 1774 |
|
|
I'm seeing this in 1778 (testing with Asus Zenfone 2 / lollipop running MMA 522) 1 run MMA and close 2 usb sync 3 wi-fi sync (successfully uses the previously created profile) 4 connect usb cable and attempt to view/configure sync settings --> it is using a brand new blank profile instead of the profile from step 2!! may be related to 0012999 (though I don't understand why Wi-Fi sync (step 3) successfully used the profile but not usb-sync (step 4). |
|
|
Fixed in MMA build 523 |
|
|
Verified 523 / 1778 |
