Search Issue Tracker
By Design
Votes
0
Found in
2018.2.2f1
Issue ID
1069094
Regression
No
[WebGL] Task awaited with Task.ConfigureAwait(false) does not continue in a WebGL build
Steps to reproduce:
1. Open user attached project
2. Build and run on WebGL
3. Observe that ConfigureAwait(false) does not output "Async task continued on <SynchronizationContext type>" and "Coroutine completed"
Expected result: Task awaited with Task.ConfigureAwait(false) should continue in a WebGL build
Reproduced in: 2018.3.0a7, 2018.2.2f1, 2018.1.9f1, 2017.4.9f1
Comments (3)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
starikcetin
Jan 02, 2024 17:58
If this is by design then you should fire the person who designed it. WTF?
Am_Un
May 04, 2021 21:31
It took couple hours to figure out that this is causing my application to die silently. How can this be by design? Is it so hard to ignore the context change on UnitySynchronizationContext?
Glader
Jan 27, 2020 02:26
By design = terrible design. Makes it nearly impossible to use WebGL with async/await.