Search Issue Tracker
By Design
Votes
0
Found in
2018.4.0f1
2019.1.0a1
2019.1.3f1
2019.2.0a1
2019.3.0a1
Issue ID
1158859
Regression
No
Uninformative errors are thrown when video fails to auto-play because of disabled auto-play in the browser settings
How to reproduce:
1. Open the attached build with a browser which does not allow video auto-play
2. Inspect the Developers console
Expected results: Error says something like "play() failed because the user didn't interact with the document first. https://goo.gl/xX8pDD"
Actual results: Error says "Uncaught (in promise) DOMException"
Reproducible with: 2018.4.2f1, 2019.1.5f1, 2019.2.0b5, 2019.3.0a5
Couldn't test with 2017.4 because of project errors after the downgrade
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
- Render Graph Execution errors when using GPU occlusion culling with 'Opaque Objects' frame setting disabled on a Camera
- Animator window: “Delete” menu item not greyed out for Base Layer context menu
- Resetting “PC_RP Asset (Universal Render Pipeline Asset)” causes Game view to become black and throws Renderer and NullReference errors in the Console window
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
Resolution Note (2019.3.X):
Firefox prints out:
Autoplay is only allowed when approved by the user, the site is activated by the user, or media is muted.
NotAllowedError: The play method is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.
In scenarios where error message or behavior is uninformative, it is recommended to check against multiple browsers in case some other browser might give better info.