Search Issue Tracker
Won't Fix
Votes
4
Found in
4.6.1f1
Issue ID
665425
Regression
Yes
[AssetServer] Commit history is lost after importing a project to 4.6.2
To Reproduce:
1. Create a project in Unity 4.5 (tested with 4.5.4f1).
2. Add this project to the Asset Server.
3. Do a couple of commits ( 2-3 should be enough)
4. Import the project in 4.6.2f1
5. Notice that the server treats the project as an entirely new one and you have to update all the previous commits from the server.
If you have any uncommitted local changes before updating you are forced to discard them (or the changes on the Server) because they are displayed as conflicts in the update window.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
Just_John
Jan 21, 2016 05:51
Just experienced this first hand switching from 5.2.1 -> 5.3.1
I didn't even realize that my changes where not being committed when I saved so I lost almost an entire game. This is very frustrating.
Wolfram
Jun 30, 2015 11:41
This is still a problem in 5.1.1!
It is important to realize the consequence of that innocent last paragraph in the description: After the upgrade from 4.5 to 5.x, Unity loses ALL(!) information about which assets are locally modified, and which ones are up-to-date. The Conflict window when trying to update will equally list unmodified(!) assets and locally changed assets as conflicts, and you have NO WAY OF KNOWING which way to resolve, unless you remember for each and every one of the listed assets (of the completely unsorted and unsortable Conflict list!) whether you need to update from the server, or need to keep your local modifiations (or whether you even HAVE modified a particular asset).
For large projects, this bug means several HOURS of tedious, manual work trying to resolve this, and bring your local copy back into a consistent state.
Please upgrade the severity of this issue!