Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
1
Found in
2021.3.15f1
2022.1.23f1
2022.2.0f1
2023.1.0a21
2023.2.0a1
2023.3.0a3
Issue ID
UUM-20411
Regression
No
"undefined symbol: WebView_loadHtml (referenced by top-level compiled C/C++ code)" errors when building a WebGL build
How to reproduce:
1. Open the attached project “Main Metabloqs ProjectFiles.zip”
2. Build the project for WebGL
Expected results: Build is successful
Actual results: Build fails with errors “Library\Bee\artifacts\WebGL\build\debug_WebGL_wasm\build.js: undefined symbol: WebView_loadHtml (referenced by top-level compiled C/C++ code)”
Reproducible with: 2021.3.15f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a21
Could not test with: 2020.3.42f1
Reproducible on: Windows 10
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
The failure is due to a linking error for a third party asset from the developer "Vuplex". External symbols are defined, but don't have any implementation in an associated .jslib file. Looking at the third party's asset content, they do in fact include a .jslib file which is missing in this project's Assets folder. The Vuplex license file refers to the "WebView for Windows and macOS" asset which is separate from the developer's WebGL asset. This could explain why the .jslib is missing (i.e. wrong platform asset).
Please reach out to the third party asset developer for any further assistance.
Resolution Note (2023.3.X):
The failure is due to a linking error for a third party asset from the developer "Vuplex". External symbols are defined, but don't have any implementation in an associated .jslib file. Looking at the third party's asset content, they do in fact include a .jslib file which is missing in this project's Assets folder. The Vuplex license file refers to the "WebView for Windows and macOS" asset which is separate from the developer's WebGL asset. This could explain why the .jslib is missing (i.e. wrong platform asset).
Please reach out to the third party asset developer for any further assistance.