Official Known issue when refactoring classes

We currently have a known issue with the Collaborate service where refactoring classes can cause Collaborate to lose track of changes to files and, if not handled correctly, loss of work. The development team is currently working on a fix for this issue and it is of the highest priority to resolve.

The issue occurs if you make changes to a script and refactor the class name within a single commit. To avoid your changes not being tracked, please make sure that any class refactoring is committed as a separate commit without making ANY other changes to the script.

If you believe that you may be at risk of being affected by this bug because you have recently refactored classes within your Project or a colleague is not receiving changes to a recently refactored class, please make a backup of your files and do the following:
1. On the workstation with the assets whose changes don’t appear to be syncing across other clients, close Unity
2. In your Project, navigate to the Library/Collab/ folder within the Project and delete the CollabSnapshot file
3. Reopen Unity and your Project. This will regenerate your snapshot file and display any missing changes in the Collab Toolbar
4. Publish these changes

We apologise for any inconvenience this may cause and will keep you all updated via this thread.

 

Hey @AdamKane,
There are still rare edge cases where this issue may still occur and we are currently working on resolving this entirely in 2018.2. The changes to 2018.3 outlined here should also fully alleviate this issue.