View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013004 | MMW v4 | Synchronization | public | 2015-12-08 10:19 | 2015-12-17 22:26 |
| Reporter | marek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1.10 | ||||
| Target Version | 4.1.10 | Fixed in Version | 4.1.10 | ||
| Summary | 0013004: Access confirmation are shown for all storages, even only one is selected | ||||
| Description | Rusty's bug - wifi sync initiated with clean MMA: Disconnect and initiate Wi-Fi Sync ==>MMW is prompted 2x in MMW to accept incoming connections from MMA (even though only the external card profile was selected) (BUG)!! ==> Pressing Back in MMA after choosing the sync location --> connection refused error! (I want to retest this--combined with the double-confirmation re. incoming connections, it's similar to http://www.ventismedia.com/mantis/view.php?id=12986 ) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1775 | ||||
|
|
Yes it will show two confirmation because MMA has to propagate new settings to MMW. MMW doesn't know that e.g. Internal storage is enabled and External storage is disabled. When MMA wants to send these new options, user has to verify both connections... |
|
|
There really should be only one confirmation, this has been already implemented in the past as 0009937 I will look into it... |
|
|
The reason why 0009937 no longer works (or rather works only for some devices) is that MMA is generating different device guid parts for both profiles based on the Rusty's log: SGH-I747M - Phone e418b5c0.0.31ff922c-c4a5-448c-8ea6-103ee0ad8105 SGH-I747M - Card 7841d761-34f7-4168-adb6-864dbcf6c6d5.1.861a86bf-4c48-4fbc-962f-01797a1d3af1 MMW compares the first part (X from X.Y.Z) that is supposed to be common for both the storages, but for some reason the Phone has e418b5c0 which seems to be serial number, but the Card has GUID, shouldn't the card has the serial number prefix too ? |
|
|
Note that on my S3 it works correctly, because the X prefix is common for the Phone and Card profiles: Phone: 32309ac73310a023.0.07e0944b-5809-45cf-b5be-7f410bd64054 Card: 32309ac73310a023.1.0f0ebf22-610d-405a-94ae-5bbb82ce2362 Both have the same prefix looking like Serial Number (32309ac73310a023) |
|
|
Alternativelly I could compare them based on the connection info IP/MAC |
|
|
Because of the variety of device/storage IDs even for the pretty same models (e.g. my S3 compared to Rusty's S3) I changed it on MMW side to compare it also based on the connection info (IP/MAC) Fixed in 4.1.10.1775 EDIT: Most probably reason for the different prefixes was that one was created by MMW and stored to storageInfo.xml.mmw (Card) and the other was created by MMA (Phone) |
|
|
Note to Ludek: I'm not quite sure how the prefixes were created differently, but I can tell you that the behavior re. the creation of the sync profiles was a bit strange and might be related; - when I plugged in the device for the first time (clean install), MMW showed two device profiles; one for the device and one for the card. I only configured the one for the card, but nonetheless each time the device was plugged into MMW, _both_ device profiles appeared. - when I subsequently performed a Wi-Fi sync operation, MMA prompted for which location to sync to (Card or Device), and I only chose to set up the Wi-Fi sync profile for the Card. After I did this, whenever I plug the device to the PC via USB, _only the card's profile appeared_ (apparently the device profile somehow became inactive). I suspect that this is how the anomalous GUID is being introduced (and wonder whether introducing other connection info will actually solve the problem if the issue is related to the original GUID being overwritten). |
|
|
No, what you have described in your last note is expected and unrelated. If you disable the Sync to this location in MMA then also in MMW it becomes disabled (i.e. Show column is unchecked for the particular profile in MMW -> Options -> Portable device sync) The reason for the different prefixes was that one was created by MMW and stored to storageInfo.xml.mmw (Card) and the other was created by MMA (Phone), this can happen if you manually delete storageInfo.xml on one of the storages (which you are doing in your tests). Comparing based on the connection info solves this issue, I am sure. |
|
|
With MMA 518 / MMW 1776, the user is prompted once in MMW to grant access, but multiple times in MMA! 1 Clean install of MMA 2 USB sync to SD card (internal memory profile enabled but not used) 3 Configure wi-fi sync (via Options > SD card) --> Prompt to choose Internal Memory OR SD card appears 4 Press SD Card --> Prompt to choose Internal Memory OR SD card appears 5 Press SD Card --> Prompt to choose Internal Memory OR SD card appears 6 Press SD Card ....this goes on and on....until the user grants access to MMA in MMW. So it appears that it's a UI problem--that the wrong dialog appears after Step 4. What should appear is a dialog indicating that MMA is waiting for MMW to grant access (we might want to add a 'cancel' button to that dialog). But instead, the same dialog appears over and over. Log DCC6AAVPBC |
|
|
Assigned to Marek, looks really like UI problem in MMA now. i.e. the spinning circle with the message about the need of acceptance comes too late (allowing user to clicks SD card over and over again). |
|
|
Re-resolving as fixed and opened a new bug at 0013015 since the most recent regression appears to be separate from the original issue, and specific to MMA. |
|
|
Verified 1778 |
