Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.4.X, 2019.1.X
Votes
0
Found in
2018.3.0a1
2019.1.0a1
2019.1.0b8
2019.2.0a1
Issue ID
1138754
Regression
Yes
PrecompiledAssemblyException does not show file paths in its message when there are few assemblies with the same name
How to reproduce:
1. Open attached project
2. Check Console Window (see screenshot below for the error)
Reproducible with: 2018.3.0a1, 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Not reproducible with: 2017.4.24f1, 2018.2.21f1
Actual results: it's impossible to tell which assembly to remove from the project, since their paths are not reported (the {0} placeholder is in the error message instead)
Expected results: there should be information regarding which assembly path has to be removed
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Add comment