This bug looks like it was 1.0.x related, so marking Fix Released.
There is a separate bug for fixing this in the newer synchronisation engine.
This bug looks like it was 1.0.x related, so marking Fix Released.
There is a separate bug for fixing this in the newer synchronisation engine.