Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0a7
Issue ID
1019951
Regression
Yes
Building a game for a non-active target without switching to it first fails
Steps to reproduce:
1. Open new Unity project
2. Open 'Build Settings' window
3. Select any non-active target DO NOT switch to it
4. Click 'Build' to build the selected target
5. Notice it fails with the following errors:
> Reload Assembly called from managed code directly. This will cause a crash. You should never refresh assets in synchronous mode or enter playmode synchronously from script code.
> ArgumentException: The Assembly UnityEditor is referenced by Unity.TextMeshPro ('Library/ScriptAssemblies/Unity.TextMeshPro.dll'). But the dll is not allowed to be included or could not be found.
Switching to the target first, or re-building after it has been switched automatically before failing will succeed.
Reproduced with: 2018.2.0a1, 2018.2.0a7
Not reproducible with: 2018.1.0b12
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment