Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.5p8
Issue ID
885803
Regression
No
[Backwards Compatibility] Crash in VerifyAssetsForBuildTarget when opening a 5.5 project in 5.3 with Cache Server enabled
Steps to reproduce:
1. Download Unity 5.3.5p8 Cache Server
2. Start the server by opening "RunOSX.command" file
3. Open the project attached on Unity 5.5.2p1 ("cache crash.zip")
4. Go to Preferences->Cache Server and select these settings:
* Cache Server Mode: Remote
* IP Address: 127.0.0.1
5. Reimport both files in asset folder to make sure cache server updates
6. Close Unity 5.5
7. Open an empty project on Unity 5.3.5p8, enable cache server with the same address.
8. Open the "cache crash" project on Unity 5.3.5p8
Result: Unity crashes in VerifyAssetsForBuildTarget(bool, AssetInterface::CancelBehaviour)
Workaround:
1. Go to cache server's directory
2. Delete contents from cache5.0 folder
3. Go to project's root folder
4. Delete "assetDatabase3" from Library folder
Note: adding full stack trace in the note
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
- Frame Debugger scrollbar gets cut off at the bottom when the Frame Debugger window is maximised
- Frame Debugger docked with the Game View can still be enabled when Game View is maximised and minimised
Add comment