Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.5f1
Issue ID
1078191
Regression
No
Package contains additional references to Unity editor libs when setting ExportPackageOptions.IncludeLibraryAssets
To reproduce:
1. Open the user's attached project
2. Build the package using the Test->Export Test Package menu at the top
3. Import the built package to a new project
Expected result: The package only contains files from the Project Settings folder
Actual result: The package contains Unity libraries and other files from the install location
Reproduced with: 2017.4.12f1, 2018.1.9f1, 2018.2.13f1, 2018.3.0b6, 2019.1.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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
The user pain for this issue is too low to invest development time. The .unitypackage format is to be replaced by a new Package Manager format in the coming year.