View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020609 | MMA | Synchronization | public | 2024-02-16 04:16 | 2024-02-16 21:37 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 2.0.0 | ||||
| Target Version | 2.0.0 | Fixed in Version | 2.0.0 | ||
| Summary | 0020609: Sync failed: unknown error (regression) | ||||
| Description | I was testing Wi-Fi sync with MMA build 1163 and MMW 2834 with one device and then while it was syncing, tried wifi syncing a second device at the same time. After a period of time, both devices had a Sync error: Unknown error! What's particularly problematic is that both devices can no longer sync--they consistently generate the error on every sync attempt! Debug log S10: TB9V26BL62 Debug log s24: HD9R2GJJIK I suspect that some sort of corruption was triggered by syncing those 2 devices at once, since a third device synced without issues. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1164 | ||||
|
|
Note: editing the sync lists in MMA had no effect (the error still occurs). After deleting the sync profile in MMW and re-attempting a Wi-Fi sync via MMA using the new profile (but without first uninstalling MMA or deleting MMA settings) the error still occurs. I was only able to solve this by deleting the profile in MMW and deleting the MMA data and cache and then resyncing from scratch! Note: even if we fix the bug that caused this situation, corruption of the sync profile should not force the user to uninstall MMA and delete the sync profile. There should be an easier way to recover from this. |
|
|
The issue seems to be related to the newer gradle version, which throws NoSuchMethodException for Java reflection. Interestingly, the issue is occurring only in the release build not in the debug build. We have to get rid of Java reflection during migration to API 34 0020335, for now, I downgrade the Gradle version to the previous one. Fixed in build 2.0.0.1164 |
|
|
Verified 1164. |
