Search Issue Tracker
Fixed in 2018.1.X
Votes
3
Found in
2017.1.0b6
Issue ID
916582
Regression
No
Generic async method does not continue on WebGL
A generic async method does not return to its caller after it finishes execution on WebGL platform
To reproduce:
1. Download attached project "BugReportProject.zip" and open in Unity
2. Open "TestScene" scene
3. Enter to Play mode
Note: Observe that these messages appear on Console:
Just a dummy log
This line will be executed
This line will not execute
Dummy
4. Exit Play mode and Build&Run project on WebGL
5. When Built Player appears on your browser, open its Console
Expected result: In Browser Console and in Editor Log you will see these messages:
Just a dummy log
This line will be executed
This line will not execute
Dummy
Actual result: In Browser Console you will see only these messages:
Just a dummy log
This line will be executed
And in Editor Log you will see these messages:
Just a dummy log
This line will be executed
This line will not execute
Dummy
Reproduced on Unity 2017.1.0b4, 2017.1.0b7 and 2017.1.0b8
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
stonstad
May 09, 2020 20:23
Correct -- still broken. https://forum.unity.com/threads/async-await-and-webgl-builds.472994/#post-5825287
imetelyov
Nov 07, 2019 09:00
Still not working in 2019.3.0b10.
SatoshiFurude
Jul 09, 2019 13:39
i have this issur with Unity 2019.1.1f1
turtlesquadron
Apr 13, 2018 11:56
Still have this issue in 2017.4 will this be back ported into 2017.1 as this is the LTS release?