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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment