0014207: Sync: new mixed profile sync issue - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0014207	MMW v4	Synchronization	public	2017-04-28 10:45	2017-05-04 18:55

Reporter	peke	Assigned To
Priority	immediate	Severity	minor	Reproducibility	have not tried
Status	resolved	Resolution	not fixable

Summary	0014207: Sync: new mixed profile sync issue
Description	When user insert newly formatted SDcard into Device and do a initial WiFi Sync MMA uses existing SDCard profile in order to sync, but then when user connect device using USB duplicate profile is created LOG File Uploaded on FTP
Steps To Reproduce	1. Eject old and Insert SDCard to Device 2. Format SDCard 3. Start MMA 4. press Sync NOW 5. Grant SDCard access 6. Check if there is some tracks to sync 7. Press Sync Now -> After sync complete Log Sent ID: ZW2I8LPEIR Description: test wifi 8. Exit MMA 9. Connect over USB -> NEW profile is created PIC attached
Tags	No tags attached.
Attached Files	Snap3.jpg (152,447 bytes) Snap3.jpg (152,447 bytes)

Fixed in build

Ludek 2017-04-28 15:33 developer ~0047868 Last edited: 2017-04-28 15:36	Peke, in the log I see that for the "XT1045 - SD card" the storageInfo.xml file wasn't found (lines 00057457 - 00057465) therefore MMW created new profile. MMW couldn't even locate the 'MediaMonkey' and 'Android' folders on the SD card. I guess it is probably again an MTP refresh issue when the files+folders does actually exist but Windows doesn't see them?? Can you confirm?

peke 2017-04-28 18:44 developer ~0047869 Last edited: 2017-04-28 18:46	All was accessible without problems and at the moment log creation I was able to access XML. That was the first thing I checked.

Ludek 2017-04-28 19:23 developer ~0047870	Based on the log it doesn't look so. Probably the device was plugged too early? Could you please re-test, but in the step 9. keep MMW closed 10) check the files via Windows Explorer 11) run DbgView 12) run MMW to see whether the duplicate profile is created or not Thanks.

Ludek 2017-04-28 20:04 developer ~0047871 Last edited: 2017-04-28 20:05	Resolving, Peke cannot reproduce anymore so it was either test error or MTP issue. In any case we can hardly do something about it. We are relying on the info from storageInfo.xml file when connected over USB -- without it is just unknown SD card for us. MMA already has some mechanisms that once storageInfo.xml is unreadable for MMW then MMA uses the pairing key from storageInfo.xml.mmw (MMW version) And MMW always prefers the info from MMA version (once accessible) and creates storageInfo.xml.mmw copy. Is related to 0014150:0047836

Ludek 2017-05-04 18:48 developer ~0047916 Last edited: 2017-05-04 18:55	I see that we have already added a workaround 0013283 that informs user when MMW has trouble getting the storageInfo.xml and doesn't show the device in MMW interface to prevent from duplicate profile creation, but this workaround did not work in your case as there was no storage enumeration error when accessing 'MediaMonkey' folder, but simply 'MediaMonkey' folder wasn't found on the SD card.