Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2018.4.0f1
2020.2
Issue ID
1214725
Regression
No
[BuildReport] Scripts are logged even when their assembly definition is excluded
Reproduction steps:
1. Open the attached project ("case_1214725-AssemblyDefinitionScripts.zip")
2. Make a standalone build
3. Check generated build's "Managed" folder and see that "ShouldNotBeAdded.dll" is not here
4. Open Editor logs and check the build report
Expected result: "Script2.cs" is not logged in the build report
Actual result: "Script2.cs" is logged in the build report, although it is not actually included in the build
Reproduces on: 2018.4.18f1, 2019.3.3f1, 2020.1.0b1, 2020.2.0a2
Couldn't test with 2017.4 (define constraints are not supported)
Notes:
1. The issue reproduces with both Mono and IL2CPP backends
2. Reproduces on both Windows and Mac
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Resolution Note:
Only critical bugs are being fixed for Build Report as it is currently unsupported in maintenance mode.