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
- Texture Sampling overlap causes graphical errors on specific Graphics APIs and Devices when using Framebuffer Fetch
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
Add comment