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:
It is also possible to debug issues on Android and iOS.
We commonly see CORS-related issues when answering support requests. Those issues can easily be avoided by reading the guidelines here.
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 :)).
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.
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.
©2015-2022 Radiant Media Player. All rights reserved.