Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2018.4
2021.1
Issue ID
1284215
Regression
No
[WebGL][macOS] Builds do not run when using Big Sur
How to reproduce:
1. Create an empty project
2. In the Build Settings, select WebGL
3. Build and run
Expected result: No errors are thrown
Actual result: UnityLoader.js throws an error
Reproducible with: 2018.4.29f1, 2019.4.15f1, 2020.1.15f1, 2020.2.0b13, 2021.1.0a1
Comments (15)
-
Richard85
Jun 10, 2021 11:18
Can Unity provide instructions for how to patch this in older versions such as 2017?
Upgrading is not always possible and it looks like some people here have a work-around.
-
nooxouille
May 17, 2021 09:09
Hi ! When building from MacOS (BigSur, m1 SoC) to a wegGL build in 2020.3.x, the said build ain't working. With the same parameters, no issue when building from w10.
This make me unable to "fully" WFH with my mbp. -
Shaolin-Dave
Apr 27, 2021 04:55
Having issues off and on, today I hit it again with 2021.1.4 while older 2021.1 versions were able to build. It's really frustrating.
-
greggman
Jan 29, 2021 01:45
Fixed in 2019.4.18f1 (didn't check versions before that)
Did notice 99% of the unity webgl games on itch.io don't run on Big Sur Chrome because of this Unity bug.
Filed a bug on Chrome just incase they want to revisit the userAgent string to work around unity's bug
bugs.chromium.org/p/chromium/issues/detail?id=1171998
-
omer_unity939
Dec 28, 2020 09:03
PERPLEX_BCN thanks ! thats a quick and easy hack :]
-
justadropofwater
Dec 21, 2020 15:27
Why is it acceptable that this is broken for almost two months for the LTS version?
-
Franzeus
Nov 30, 2020 10:54
We did kind of a small hack to fix it. Basically we overwrite the userAgent to a working version and set it back:
/**
* Overwriting the UnityLoader to fix a bug in their regular expression for Mac OS X 11+
*/
(function() {
if (!window["UnityLoader"]) return;// Get OS Version (Intel Mac OS X 11_0)
var os_version = /Mac OS X ([\.\_\d]+)/.exec(navigator.userAgent);
if (os_version && os_version[1]) {
// Extract "10_15_7" -> 10
os_version = parseInt(os_version[1].split("_")[0], 10);
}// The issue occured with Mac OS X 11+
if (os_version && os_version >= 11) {UnityLoader.OriginalSystemInfo = UnityLoader.SystemInfo;
UnityLoader.SystemInfo = function() {
try {
return UnityLoader.OriginalSystemInfo();
} catch () {
var original_ua = navigator.userAgent;// Overwrite the user agent with a one we know was working:
var valid_ua = navigator.userAgent.replace(/Mac OS X ([\.\_\d]+)/, "Mac OS X 10_15_7");
window.navigator.__defineGetter__('userAgent', function () {
return valid_ua;
});var result = UnityLoader.OriginalSystemInfo();
// Restore original userAgent
window.navigator.__defineGetter__('userAgent', function () {
return original_ua;
});return result;
}
};
}})();
Obviously this script has to get loaded after the UnityLoader.js
-
roy_tangelogames
Nov 25, 2020 10:48
Will you support it in the next 2019 patch as well?
Unfortunately we have games which were developed in older versions then 2021. -
jeffreylanters
Nov 25, 2020 10:42
Same here, happens on Chrome (all versions) only. Safari 14.0.1 seems to bypass this Regex.
-
bradenroper
Nov 24, 2020 15:00
Is this issue only on the dev side? We have a lot of WebGL games that we build on Windows machines that are throwing an error when being played on Chrome in Big Sur. It would be nice to know if it's an issue with Chrome on Big Sur or the OS itself, because a lot of our Unity games were built with various older versions of Unity and were not planned for updates just yet.
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note (fix version 2021.1):
Fixed in Unity 2021.1.0a2 and above
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b12
Resolution Note (fix version 2019.4):
Fixed in 2019.4.21f1