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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment