View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013736 | MMA | Synchronization | public | 2016-12-09 16:36 | 2017-03-08 21:53 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.2.0 | ||||
| Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
| Summary | 0013736: Wi-Fi sync connection fails without indicating that an alternative server is available | ||||
| Description | This may be a known limitation of how sync currently works, but I suspect that it might be a cause of some of the reports in which MMA can't connect to a server. Moreover, I expect that as users test MM5, this will become a more common scenario: 1) Wi-Fi sync with instance 1 of MMW 5 (or 4, though not tested) portable 2) Install new portable version of MM5 without importing the db 3) Run MMA and attempt to connect to the server to configure Sync --> MMA fails to connect to the server This is 100% reproducible. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 624 | ||||
| related to | 0012723 | closed | martin | MMA | Better management of connection errors |
| has duplicate | 0010098 | resolved | rusty | MMA | Nicer handling of failed connection to the server |
| related to | 0013361 | feedback | rusty | MMA | Improve error handling in case of disabled sync profiles |
| related to | 0011780 | assigned | martin | MMA | WiFi Sync Settings: Each SSID should have own settings |
|
|
I found the same today, but it was caused by change of the sync server. i.e. portable version of MM4/MM5 creates another server instance. To fix this I needed to change the sync server in in MMA > Options > Choose sync server Maybe MMA should announce that another sync server is presented ? (i.e. if it fails to connect to the old server and another is detected) |
|
|
Yes--that's the problem. In both Steps 1 and 3 I had accessed sync settings for 'Nexus 5x internal storage', without realizing that they were two different device profiles. The solution suggested by Ludek is that rather than just resulting in an error message re. a failed connection, MMA should indicate that another sync server is available. e.g. Show the existing connection error message, but add the following if another sync server was detected/exists (and switch to the select sync server panel): Try connecting to a different sync server. |
|
|
It should be fixed as part of 0012723 |
|
|
I'm also experiencing BUg. Tested on MM4.x and it works. |
|
|
The problem is that we need this fixed before we post the MM5 beta since many users are likely to face the issue. Is it not possible to create a quick fix? |
|
|
Quick fix in build 1.2.0.623 |
|
|
Verified 623 |
|
|
I just tested this out in 623, and although pressing 'Sync' resulted in the error message appearing, BUT pressing 'Nexus 5x internal storage' in the Options > Sync settings resulted failed to generate the error message. Log ID: 2ASH99QAW7 |
|
|
Fixed in builds 624 and 658 |
|
|
Verified 624 and 658 on these android versions: 4.1.2 INT and SDCard 4.2.2 INT and SDCard 5.1 INT and SDCard 6.0.1 INT and SDCard |
|
|
Verified 625 with Nexus 5x Android 7. |
