Most modern browsers offer a debug console, which allows you to view logs as commands are executed by the browser.
- On a Windows computer, press
F12and click the console tab.
- On a Mac, press
Shift+Apple+Iand click the console tab.
For developing and testing live video, it's always best to use two independent computers. If you don't have a second machine available, we recommend using at least a second browser, such as Chrome and Firefox. Remember, when running multiple tabs or windows in the same browser, some features may not work as expected because the browser session is shared.
If you are using Chrome as your first browser, you may also download Chrome Canary which will function as second fully independent browser but without it nagging you to make it the default browser. Canary is the latest Chrome developer build, approximately 3 months ahead of Chrome.
The SDK logs warnings and errors to the browser console. You should observe these when debugging. Log messages often contain a link which explains possible situations further.
When a development API key is in use, we will also display status information about possible issues on a banner in the lower left corner of the page. The banner won't be shown once you switch to the production API key, and we'll also reduce the number of logs being shown in production.
A helpful tool for finding out what's wrong with a JSON Web Token (JWT) is the official JWT debugger, which allows you to create and validate tokens against the project secret. When working tokens, make sure the "secret base64 encoded" checkbox is selected because our secret is Base64-encoded already.