That is normal behavior and won't affect final users in any way: some browsers won't allow audio to be played by our library (on scan) if the user hasn't first touched/clicked the page, and will block the first audio initialization calls (outside from normal JavaScript code execution). Audio will, however, play as expected after the first user interaction.
Why can I see warning messages "The AudioContext was not allowed to start" in the console?
Have more questions? Submit a request