Radiant Media Player

Debugging guide



Guide sections


Use your browser developer tools

When implementing or debugging Radiant Media Player in your application your browser developer tools are your best friends. Those are commonly available in modern browsers:

Specifically you are going to want to look at 3 sections of your browser developer tools:

  • The Elements/Inspectors tab: here you can inspect Radiant Media Player DOM layout and see which CSS rules are applied to each element.
  • The console tab: if the player encounter an error it is likely to be printed here. Also when using Radiant Media Player debug mode (see next section) player logs will be printed in the console.
  • The network tab: this is where you can see network requests made by the player and errors when they happen. Reviewing HTTP status codes for files requested by the player can help in identifying the root cause of most common network issues. Analysing the Request & Response Headers for each request may also prove useful.

It is also possible to debug issues on Android and iOS.


CORS issues

We commonly see CORS-related issues when answering support requests. Those issues can easily be avoided by reading the guidelines here.


Radiant Media Player debug mode


Player debug file

Since Radiant Media Player 4 the main player JavaScript debug file is separated from the production player JavaScript file. You can load the player JavaScript debug file as:

https://cdn.radiantmediatechs.com/rmp/v4/latest/js/rmp.debug.js

Or for a specific version:

https://cdn.radiantmediatechs.com/rmp/4.6.11/js/rmp.debug.js

The player debug file is also available in the self-hosted package.

This player debug file automatically prints to the browser console useful information about the player inner-workings helping to pinpoint the source of issues when they occur.

Never use the debug player file in production - it will run slower than the production player file


Debug player setting

debugLevel: Number

This setting set the log level within the browser console. Default is 1 which means that a good but limited amount of logs are printed to the console. Set this value to 2 to print all player logs (it is going to print a lot of things :)).


Debugging issues on mobile devices


Chrome for Android

Google has a comprehensive guide for Remote Debugging Android Devices. As such you can plug an Android device to a Windows, Mac, or Linux computer and access various tools for debugging through Desktop Google Chrome DevTools. This allows to troubleshoot issues on Chrome for Android and in Android WebViews.


iOS Safari

Similar to the set of tools provided by Google for debugging Android devices, Apple provides a set of tools to debug issues on iOS Safari. The difference is that you will need a Mac computer to use those tools through Desktop Safari. Instructions for using Safari web inspector, including on Safari on iOS, can be found on Apple website here.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 3.0 License.