When implementing or debugging Radiant Media Player within your application your browser developer tools are your best friends. Those commonly available in modern browsers:
It is also possible to remote debug Chrome for Android devices. You can also debug iOS Safari if you have a macOS computer.
Specifically you are going to need to look at 3 sections of your browser developer tools:
We commonly see CORS-related issues when answering support requests. Those issues can easily be avoided by reading the guidelines here.
Or for a specific version:
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
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 :)).