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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment