Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b8
Issue ID
1006487
Regression
No
Build fails when the Editor files are in the same Assembly Definition as normal Monobehaviours
To reproduce:
1. Open the project, attached by the tester (New Unity Project.zip)
2. Build the project for PC standalone
Expected: the build succeeds
Reproduced in 2018.1.0b1, 2018.1.0b8, 2018.2.0a2
Could not test in 2017.3 due to many errors in the packages
By design:
"Editor" folder has no special meaning inside .asmdef folders. Editor folder must have a separate .asmdef file that is marked as being compatible with the editor only.
As documented here:
https://docs.unity3d.com/Manual/ScriptCompilationAssemblyDefinitionFiles.html
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment