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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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.