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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
- [Linux] Bug Reporter window is in Light mode when the Editor theme is Dark mode
Resolution Note:
Only critical bugs are being fixed for Build Report as it is currently unsupported in maintenance mode.