Search Issue Tracker
Duplicate
Votes
0
Found in
2021.2.0a17
2021.2.0b1
Issue ID
1346712
Regression
Yes
WebGL build fails with libraries in "external packages" or scoped package registries
-e: when you use a package located outside of your local unity project on in a scoped package registry the WebGL build will fail
-repro:
--extract attached archive and open the project with latest Unity
--start a WebGL build
--NOTICE it fails with errors
--copy the package folder from the root of the extracted folder into UnityProject/Packages#
--remove the external linking in the manifest.json file
--start a WebGL build
--NOTICE it finishes the build and works
-additional notes:
--this already fails using with alpha 17 when the incremental pipeline was introduced
--the build failing behaviour can be seen when using a scoped registry to include a packages such as https://openupm.com/packages/com.atteneder.draco/?subPage=readme
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
This is a duplicate of issue #1337939