Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.3.0a1
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1128939
Regression
No
Unity packages are unnecessarily recompiled when any assembly definition are modified
Steps to reproduce:
1. Download and open the attached project
2. Create or delete an Assembly Definition
Expected result: only Assembly-CSharp-Editor.dll and referenced assemblies are recompiled
Actual result: all assemblies from Packages are recompiled, resulting in wasted time
Reproduced on 2018.3.0a1, 2018.3.6f1, 2019.1.0b4, 2019.2.0a6
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on Umbra::QueryExt::queryStaticShadowCasters when opening a specific project
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when opening a specific project
- Shader variants are recompiled while Building when the Platform is switched and changed back after the first Build
- Crash on memcpy when importing lightmaps after GI bake
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
Resolution Note:
This is currently by design. All .asmdef assemblies are recompiled when an .asmdef file is modified. However, only the required .asmdefs are recompiled when C# scripts change.
We have it on our backlog to improve this for the future.