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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment