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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.