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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1337939