Skip to main content
Throne Debugging Guide
Updated over a year ago

We are very sorry you ran into a bug. We try to make the software as stable as possible but between multiple devices and operating systems, errors can happen. Sometimes things like browser extensions and VPNs can interfere with Throne's services, so you may want to try disabling those first.

If you are reading this guide, chances are we weren’t able to reproduce your error. This guide is to help you help our engineering team solve your issue.

Please send us the following information to: [email protected]

Chrome

Step 1: reload the page

Refresh the page you experience the error on.

Step 2: open the developers console

MacOs: Option + ⌘ + J (on macOS)

Window/Linux: Shift + CTRL + J

Step 3: click on the “console” part of the developers console

mceclip0.png

Step 4: clear the console (so it is clean for us)

Chrome

mceclip1.png

Step 5: do the action that produced the error

Step 6: send us full screenshots of everything that was added to the log whilst you were trying to reproduce the error

Firefox

Step 1: reload the page

Refresh the page you experience the error on.

Step 2: open the developers console

You must be on a computer on this. This will not work for phones

MacOs: Option + ⌘ + K (on macOS)

Window/Linux: Shift + CTRL + K

Step 3: click on the “console” part of the developers console

mceclip2.png

Step 4: clear the console (so it is clean for us)

mceclip3.png

Step 5: do the action that produced the error

Step 6: send us full screenshots of everything that was added to the log whilst you were trying to reproduce the error

Safari

Step 1: reload the page

Refresh the page you experience the error on.

Step 2: open the developers console

You must be on a computer on this. This will not work for phones

Press: Option + ⌘ + C

Step 3: click on the “console” part of the developers console

mceclip4.png

Step 4: clear the console (so it is clean for us)

mceclip5.png

Step 5: do the action that produced the error

Step 6: send us full screenshots of everything that was added to the log whilst you were trying to reproduce the error

Did this answer your question?