Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0p2
Issue ID
938953
Regression
No
Build failure because of UnityEditor namespace causes script references to be lost
How to reproduce:
1. Open the "BuildFailure" project
2. Open the "main" scene
3. Press Play (notice the script "hello" is working)
4 Try to build the project
5 Press Play again, the script reference is missing
Expected Result: The build failure doesn't affect the Editor.
Actual Result: The script references in the scene are lost.
Reproducible with: 2017.1.0p3, 5.6.3f1, 5.5.4p2.
Not reproducible with: 2017.3.0a3, 2017.2.0b6.
Note: with 5.6.3f1 and 5.5.4p2 the script references are not lost, but Unity won't let you enter play mode because of "compiler error".
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
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
This is a duplicate of issue #921652