Search Issue Tracker
Third Party Issue
Third Party Issue in 2020.3.X
Votes
0
Found in
2020.3.42f1
Issue ID
UUM-37102
Regression
No
Error “TypeError: Cannot read properties of undefined (reading ’getSupportedExtensions')" is thrown and WebGL builds do not run on ChromeOS devices when using WebGL 1.0 Graphics API
How to reproduce:
1. Open the attached “UnityProject_2020.3.42f1.zip” project
2. Press File → Build Settings
3. Make sure WebGL is selected as Platform
4. Press Build
5. Host build folder through Xampp localhost server
6. Launch the build on the ChromeOS device
Expected result: Player launches
Actual result: Player hanging on loading and the error “TypeError: Cannot read properties of undefined (reading ’getSupportedExtensions') is thrown
Reproducible with: 2020.3.42f1
Testing environment: Windows 10 (user reported)
Reproducible on this OS:
ChromeOS 112.0.5615.134
Notes:
- CQA couldn't reproduce this issue
- CQA tested on these devices:
VLNQA00345 - Asus Chromebook CT100PA
VLNQA00473 - AMD Stoney Ridge Chromebook
Users notes:
- MRA is forcing WebGL 1.0 (Unity 2020)
- MMA is using auto graphics (Unity 2018)
- User mentions this issue is not reproducible with the 2022.2 stream
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
This issue was fixed by the Chrome team in Chrome version 115.
Resolution Note (2020.3.X):
This issue was fixed by the Chrome team in Chrome version 115.