View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018318 | MMA | Synchronization | public | 2021-09-19 15:45 | 2022-12-20 22:38 |
| 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 | 0018318: Duplicate sync profile / problems with 2.0 (regression) | ||||
| Description | Upon attempting to sync with 2.0, using an existing profile from 1.x, a duplicate profile was created. New Profile: Google Pixel 2 XL - Internal shared storage Old profile: was renamed to "" The sync operation then: - synced tracks from a playlist (Mix 3) that was checked on the auto-sync list - did not delete unselected tracks ! - did not create the playlist on the device! I suspect that the problem stems from the fact that a duplicate profile was created on the initial sync. This may be because the IP address of the MM5 machine changed. Log ID (from a second sync operation--after a duplicate profile had already been created): EI89CL16AC | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1013 | ||||
|
|
Further testing reveals that duplicate servers are created every time MMA attempts to authenticate ("An unknown portable device is attempting to sync with the MediaMonkey Library for the first time.... Do you want to grant it access?..."). This appears to be related to MM5 presenting the authentication dialog first when the MMA user clicks 'Select sync server' > <SyncServerName>, and then a second time when the MMA user attempts to choose which 'Server content' to sync. What ends up happening is that some config settings (e.g. track deletion settings) are then saved with the initially created profile (Google Pixel 2 XL - Internal shared storage) and others (e.g. sync list) are associated with the second profile (""). This bug makes it impossible to properly sync MMA 2. |
|
|
Retested on a clean install of MMA (after having deleted sync profiles in MM5) and the issue still occurs. So it is currently not possible to set up and initiate synchronization with MMW5 from MMA. The workaround is to: 1 Initiate configuration via MMA 2 In MMW5, delete the "" profile, and configure the server content to sync (this way the sync list is associated with the correct profile and a new one isn't created) 3 In MMA initiate the sync |
|
|
I can't replicate. I have 20+ devices in that test build and not a single issue with 1010. Tested upgrade, Clean/New profile MM5. |
|
|
Note that the sync profile is stored within MM5.DB so if you deleted the profile in MM5 (or not used MM5.DB/settings previously used for the same device) then new profile creation is expected. EDIT: Based on the Rusty's video there are by evidence two profiles created, so I think MMA erroneously sends two different sync keys (profile IDs). The first one with key '9ec46b44-eee2-368c-8104-61ada296bf73.0.63d061ae-3381-48fe-bf9d-6fd9d637e2cb' based on MMA's request: /DeviceID=9ec46b44-eee2-368c-8104-61ada296bf73.0.63d061ae-3381-48fe-bf9d-6fd9d637e2cb_DeviceName=Google Pixel 2 XL - Internal shared storage_ItemID=DeviceConfig.xml And the second (empty) profile with empty name based on MMA's request: SyncItems:DeviceID:null So the problem is in the request 'SyncItems:DeviceID:null' that should be 'SyncItems:DeviceID:9ec46b44-eee2-368c-8104-61ada296bf73.0.63d061ae-3381-48fe-bf9d-6fd9d637e2cb' |
|
|
Fixed in build 2.0.0.1013 |
|
|
Verified 1054 |
