Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.1.X, 2017.2.X, 2017.4.X, 2018.1.X
Votes
0
Found in
2017.1.1f1
Issue ID
952569
Regression
No
[UnityYAMLMerge] Collab sometimes overwrites asset with older copy during merge, losing data
Collaborate starts loosing changes in the scene after updating. Pressing revert, it reverts to the last update, which also looses all the changes made in the scene, even though scene is saved.
To reproduce:
1. Create a new collaborate project
2. On the first machine make some changes and save the scene
3. On the second machine also make some changes and save the scene
4. On the first machine push the changes to the cloud
5. On the second machine update the project
6. Repeat steps 2 - 5 and after couple of times the bug starts to reproduce all the time
Expected result: scene is updated but the changes done locally are kept
Actual result: changes made to the scene are lost
Reproduced on: 5.5.5f1 5.6.3f1 2017.1.1f1 2017.3.0b3 spin#2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment