First, if you are an author of a Unity game, you can resolve the issue by updating and rebuilding your Unity project using one of:ī.

Now we are (quite painfully so) aware that older already deployed Unity games are unable to run on this Chrome version.Ī. What caught us by surprise was that the same issue that Unity had with the pre-release version of Safari Beta channel, also now unsurfaced in Chrome 88 Stable release. Chrome has a tracking bug for the same here. Firefox has the UA string also frozen for Big Sur. It looks like Apple had done just that with the macOS Big Sur release. In the past year, there has been intent for browser vendors to 'freeze and mask' navigator user agent strings in time, deprecating erAgent to avoid increasing fingerprinting possibilities on the web. The root cause of the issue was an old piece of system information identification script in Unity that was not robustly future proof to major OS version number changes. Or the progress bar hangs at 0%, and observing the web page console prints the same error.īack then, patches were deployed to all Unity release channels like Emily mentions, though when it came time to release, it looks like Apple actually froze Safari's user agent to an earlier version, sidestepping the problem altogether, hence the fixes were not needed after all for Safari. Uncaught TypeError: Cannot read property '1' of null This issue was originally reported against macOS Beta in, where it was noticed that pre-release Safari in macOS beta channel was unable to run Unity WebGL builds.Ī symptom of this issue was an error box at page startup, that prints

Is unity web player safe for mac