Search Issue Tracker
By Design
By Design in 2022.2.X
Votes
0
Found in
2020.3.35f1
2021.3.3f1
2022.1.3f1
2022.2.0a13
Issue ID
UUM-635
Regression
No
Files from unused packages are not stripped from the build
Reproduction steps:
1. Open the user's attached project "Minimal Build Stripping.zip"
2. Build the project
3. Observe the Build Report in the Editor.log
Expected result: Files from packages that are not used are not included in the build
Actual result: Files from packages such as uGUI, Visual Scripting and Test Framework are included even though they are not used
Reproducible with: 2019.4.37f1, 2020.3.33f1, 2021.3.0f1, 2022.1.0b15, 2022.2.0a10
Note: Reproducible with different build targets
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
The build picks up dependencies based on the Scenes/Assets being built in the user project and also packages that are in use. Packages sometimes add dependencies via Resource folders. In testing this provided project in a recent build of Unity I observed the same "Debug" assets that are mentioned in https://forum.unity.com/threads/legacy-ui.1229454. These come from the Core RP project and are currently expected in the build to support the RenderingDebugging feature. The team is aware of the need to remove that forced inclusion in a future version. In general we will continue to work to keep package dependencies modest. In cases where there is some apparent bug that is bringing in extra unnecessary dependencies we will appreciate further bug reports. If the bug report is focused on specific objects then we would be able to turn it into an trackable and actionable bug fix.
Resolution Note (2022.2.X):
The build picks up dependencies based on the Scenes/Assets being built in the user project and also packages that are in use. Packages sometimes add dependencies via Resource folders. In testing this provided project in a recent build of Unity I observed the same "Debug" assets that are mentioned in https://forum.unity.com/threads/legacy-ui.1229454. These come from the Core RP project and are currently expected in the build to support the RenderingDebugging feature. The team is aware of the need to remove that forced inclusion in a future version. In general we will continue to work to keep package dependencies modest. In cases where there is some apparent bug that is bringing in extra unnecessary dependencies we will appreciate further bug reports. If the bug report is focused on specific objects then we would be able to turn it into an trackable and actionable bug fix.