View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012842 | MMW v4 | Synchronization | public | 2015-09-02 17:32 | 2015-09-07 08:40 |
| Reporter | marek | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | random |
| Status | closed | Resolution | fixed | ||
| Platform | Windows | OS | 7 | OS Version | - |
| Product Version | 4.1.9 | ||||
| Target Version | 4.1.9 | Fixed in Version | 4.1.9 | ||
| Summary | 0012842: StorageInfo.xml.MMW is sometimes overwritten | ||||
| Description | I have twice reproduced situation that is probably described by user here: GJX-899-76959 The issue is in overwriting of StorageInfo.xml.MMW and duplicating of profiles. in attached log: 1. storageInfo.xml.MMW contained GUID: dd431370-c05a-471a-acce-9c11882297c6.1.68748256-4d08-44d3-baf1-5a550a527273 2. MMA was installed and storageInfo.xml.MMW parsed this GUID. 3. NOW SOMEHOW THE XML WAS OVERWRITTEN BY MMW 4. MMA was uninstalled - storageInfo.xml was deleted due to Lollipop restrictions (it was stored in /Android/data/com..../files/files) 5. MMA was reinstalled and storageInfo.xml.MMW was parsed again - because this xml acts as backup of GUID. BUT now the GUID is: c9d98649-69c0-4c7a-a2f8-a198d4aaf52b.1.3db1a345-e715-4582-8478-bc26396f06ce 6. MMW requests new confirmation during sync and profiles are duplicated! NOTE: I was also able to replicate strange issue when request was for internal card but MMW requested allow external card. This might be the cause of mixing of storages. But I have logs only from build 1746. I am trying to replicate in current build but it might be already fixed. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1754 | ||||
|
|
yes, I noticed this issue while fixing 0012820 and fixed it So this has been already fixed in build 4.1.9.1754 |
|
|
The logs and reproduce steps, that I attached, are from 1755. The NOTE is related to similar, maybe related, issue. I am sorry for confusion. |
|
|
As talked over IM, Marek is testing further to clarify whether the issue still exists or not |
|
|
Marek confirmed that it is fixed in 1754, re-resolving |
|
|
Verified 1757 |
