05-18-2022, 09:58 AM
Hello Steven,
The only code that was modified with version 3.5.3 related to the synchronization functionality was to properly handle canceling out when you are prompted to select a file when a conflict occurs where MobileSheets can't properly match up songs on each devices. That should have no impact on the way in which the sync proceeds normally. So I'm not sure why you are seeing that behavior, but it's certainly not new to 3.5.3. What's strange about the issue you reported is that the code is set up so that the server waits until it receives a message from the client indicating that the client has finished processing changes on its end (the transferring of necessary files and such). If you are seeing the sync finish on the server tablet, that means it got the message it wanted from the client indicating the sync was complete even though the client tablet only showed 3% completion. I have no idea how that is possible. I can't reproduce that myself so I'm not sure how to go about investigating it at the moment. I'll have to spend some time with test libraries seeing if I can figure out some way to see that behavior. How large is the library you are working with?
Thanks,
Mike
The only code that was modified with version 3.5.3 related to the synchronization functionality was to properly handle canceling out when you are prompted to select a file when a conflict occurs where MobileSheets can't properly match up songs on each devices. That should have no impact on the way in which the sync proceeds normally. So I'm not sure why you are seeing that behavior, but it's certainly not new to 3.5.3. What's strange about the issue you reported is that the code is set up so that the server waits until it receives a message from the client indicating that the client has finished processing changes on its end (the transferring of necessary files and such). If you are seeing the sync finish on the server tablet, that means it got the message it wanted from the client indicating the sync was complete even though the client tablet only showed 3% completion. I have no idea how that is possible. I can't reproduce that myself so I'm not sure how to go about investigating it at the moment. I'll have to spend some time with test libraries seeing if I can figure out some way to see that behavior. How large is the library you are working with?
Thanks,
Mike