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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment