Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.1.X, 2018.2.X
Votes
7
Found in
5.5.0f3
Issue ID
1003917
Regression
Yes
Chrome66: Autoplaying audio is muted
-e: see title, scene stays silent, message about changed behaviour being logged in console
--regression with Chrome, not Unity
-repro:
--open attached project
--build and run in Chrome66 (current dev release)
--NOTICE the scene stays silent and message being logged:
The AudioContext was not allowed to start. It must be resume (or created) after a user gesture on the page. https://goo.gl/7K7WLu
Workaround: See https://forum.unity.com/threads/chrome-on-the-dev-branch-version-66-may-block-audio-for-unity-webgl.517758/#post-3463792
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "GUI Error: Invalid GUILayout state in ConsoleWindow view" and "NullReferenceException" errors are thrown when pinging GameObject in inactive Hierarchy from Console
- Crash on profiling::Dispatcher::AcquireFreeBuffer when the Editor's profiler session acquires a new dispatch buffer to emit UI events
- [XRIT] CurveVisualController causes "Invalid AABB" and "IsFinite(distanceForSort)" errors when startup endpoint equals origin
- Building with -nographics breaks VFX Graph Position (Depth) as an Operator
- MacOS server cannot find libMonoPosixHelper.dylib when calling GZipStream
Add comment