Search Issue Tracker
By Design
Votes
0
Found in
2018.2.0a1
2018.2.4f1
Issue ID
1091781
Regression
No
Build-in Packages modules are being included in the project folder when they are disabled in the Package manager
To reproduce:
1. Create a new project for android
2. Go to package manager window
3. Choose Built-in Packages
4. Disable any of the packages there
5. Build the scene
Actual result: The modules of disabled packages are still included in the project folder
Expected result: The modules should not be included in the "Managed" folder of the project if they are disabled
Reproduced with: 2018.2.0a1; 2018.2.16f1; 2018.3.0a1;2018.3.0b10; 2019.1.0a1; 2019.1.0a9
Note: adding pictures.
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 vkGetInstanceProcAddr when setting graphics API to "Vulkan" on Fantasy Kingdom learning project
- Overlay Camera "clear depth" not working on Vulkan+Pixel8
- Shadows from Shadow Caster 2D using 2D Colliders show incorrectly when tiles are removed at runtime
- Stencil buffer is incorrectly cleared across Vulkan render passes during depth-only clear operations when using CommandBuffer API
- A non-existent webpage is opened when "Learn about Unity Build Automation" hyperlink is clicked
Resolution Note:
This is expected. Stripping of engine internals is only supported on platforms which have the "Strip Engine Code" Player Setting (and have that enabled) - https://docs.unity3d.com/ScriptReference/PlayerSettings-stripEngineCode.html