Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.1.0a1
2019.2.17f1
Issue ID
1206736
Regression
Yes
WebGL builds will sometimes fail to launch without error when using Build and Run
WebGL builds will sometimes fail to launch without error when using Build and Run
When working with a WebGL project in Unity, if the user uses the "Build and Run" feature to start the player, sometimes (2/5) the Editor will fail to launch the Player with no errors.
Reproduced in: 2019.1, 2019.2, 2019.3, 2020.1
Steps to reproduce:
- Create a new project in Unity with WebGL build support installed
- Switch the project platform to WebGL (File > Build Settings > WebGL > Switch Platform)
- Build and Run
- Observe the editor will build and launch the player
- Repeat the Build and Run steps, observing sometimes (2/5) the editor will fail to launch the WebGL player without any error other than provided by the browser trying to access the resource
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
- Some UI Toolkit pixels are transparent when not all corners are rounded
- The default layout file gets corrupted when the project is saved and closed after running a specific Test Runner test
- Cameras overlay sometimes show “No Cameras” for a split second instead of “Main Camera” when clicked to move the overlay
- Sprite Mode defaults to "Multiple" instead of "Single" when switching the Texture Type to "Sprite (2D and UI)"
- Adaptive Probe Volume “Open” button closes the existing RPAsset window and opens a new RPAsset window instead of focusing the existing RPAsset window
Resolution Note (fix version 2020.1):
Could not reproduce issue as reported in 2020.0a19, closing as fixed.