All Collections
Troubleshooting and errors
Share a screenshot of a JavaScript console error
Share a screenshot of a JavaScript console error

Learn how to help SendBoard engineers troubleshoot JavaScript errors that might occur in your web browser

Mark Fowles avatar
Written by Mark Fowles
Updated over a week ago

For some issues, we may request that you send us a screenshot of your browser's JavaScript console.

This guide shows how to access the JavaScript Console using popular browsers.


How to capture the JavaScript console error

Step 1 - Capture the error

After you experience an error:

  1. Open your browser's Javascript console. See below for browser-specific steps.

  2. Refresh your browser.

  3. Re-create the error.

  4. Take a screenshot including the contents of the Javascript console.

If you don't refresh your browser, the Javascript console won't display the error, which we need to see in order to troubleshoot.


We've listed the steps for different browsers below:

Chrome

Use the keyboard shortcut:

  • Mac - ⌘ + Option + J

  • Windows - Ctrl + Shift + J

Or use these steps:

Mac

  1. Click View.

  2. Select Developer.

  3. Select JavaScript Console.

Windows

  1. Click the menu icon.

  2. Select Tools.

  3. Select JavaScript Console.


Safari

Use the keyboard shortcut:

  • ⌘ + Option + C

Or use these steps:

  1. Click Safari.

  2. Select Preferences.

  3. In the Advanced tab, check Show Develop menu in menu bar.

  4. Click Develop.

  5. Select Show JavaScript Console.


Firefox

Use a keyboard shortcut:

  • Mac - ⌘ + Shift + J

  • Windows - Ctrl + Shift + J

Or use the steps:

Mac

  1. Click Tools.

  2. Select Web Developer.

  3. Select Browser Console.

Windows

  1. Click Firefox.

  2. Select Web Developer.

  3. Select Browser Console.


Internet Explorer and Microsoft Edge

Use this keyboard shortcut: F12

Or use these steps:

  1. Click the Settings Cog icon.

  2. Select F12 Developer Tools.


Step 2 - send us a screenshot

After you've accessed the JavaScript Console and refreshed your browser, share a screenshot of the error with our team.

Did this answer your question?