Quick solutions to common player related issues
This message appears in the player if the player either misses a token or uses an invalid token. The troubleshooting scenario is slightly different depending on the type of embed you are using.
This is a tricky one by an arcane spec known as named acccess on the window object. Which means if you create an element with and
id that conflicts with a umd global, you might find unexpected problems for yourself. This is especially important in single-page applications where DOM nodes maybe both rendered and removed very quickly during a session.
As a rule never create elements that have ids which conflict with umd namespaces.
// import the flowplayer umd <script src="https://cdn.flowplayer.com/releases/native/stable/default/flowplayer.js"> // uh oh, we just removed the umd <div id="flowplayer"> // attempt to create a flowplayer instance <script> // flowplayer umd is now the `<div>` element // browsers implicitly add global variables to // the window object by DOM id flowplayer("#flowplayer") </script>
it is possible to add an
async attribute to a
<script> tag, and some resources tout this as a way to speed up webpage loading.
Generally speaking, do not add
async to our asset tags
We care deeply about performance, and have spent many painstaking hours reducing our bundled code size and optimizing it for gzip compression, usually the bottleneck is not with us, but if you are still unconvinced please ping us on support and we will see if we cannot help with your problem.
Below is a list of third party libraries that are known to cause potential problems either for playback or ad playback. We recommmend thorough testing before using these libraries simultaneously with Flowplayer.