Browser Console Logs
=====================

When troubleshooting an issue in TeamHub, support may ask you for your browser's **console log**. This is a technical log, hidden by default, that records errors and diagnostic messages from the page — it often pins down the cause of a problem far faster than a description alone.

This page shows how to open the console and copy its contents in each supported browser. See :doc:`support` for how browser issues should be reported, and general information on which browsers we support.

Before You Start
-----------------

* Reproduce the issue with the console open, if you can — this captures the errors as they happen rather than relying on messages left over from earlier.
* Enable **Preserve Log** (Chrome, Edge) or the equivalent option before reproducing the issue, so a page reload or redirect doesn't clear the log.
* Include a screenshot of the console alongside the copied text if anything is unclear — see :doc:`support` for the full list of what to include when reporting a browser issue.

Chrome
------

1. Open the developer tools:

   * Windows/Linux — press ``F12`` or ``Ctrl+Shift+J``
   * Mac — press ``Cmd+Option+J``
   * Or use the menu: **⋮ (top right)** → **More tools** → **Developer tools**, then select the **Console** tab.

2. Right-click **Preserve log** and enable it (checkbox near the top of the panel) if you need to reproduce the issue first.
3. Reproduce the issue.
4. Right-click anywhere inside the console output and choose **Save as...** to export the full log to a file, or select the relevant messages and press ``Ctrl+C`` / ``Cmd+C`` to copy them.
5. Paste the copied text into your support email, or attach the saved file.

Firefox
-------

1. Open the developer tools:

   * Windows/Linux — press ``F12`` or ``Ctrl+Shift+K``
   * Mac — press ``Cmd+Option+K``
   * Or use the menu: **☰** → **More tools** → **Web Developer Tools**, then select the **Console** tab.

2. Click the gear icon in the console panel and enable **Persist Logs** if you need to reproduce the issue first.
3. Reproduce the issue.
4. Right-click anywhere inside the console output and choose **Export Visible Messages To** → **Clipboard** (or **File**) to copy or save the log. Alternatively, select the messages you need and press ``Ctrl+C`` / ``Cmd+C``.
5. Paste the copied text into your support email, or attach the saved file.

Edge
----

Edge is built on the same engine as Chrome, so the steps are identical:

1. Open the developer tools:

   * Windows/Linux — press ``F12`` or ``Ctrl+Shift+J``
   * Mac — press ``Cmd+Option+J``
   * Or use the menu: **... (top right)** → **More tools** → **Developer tools**, then select the **Console** tab.

2. Right-click **Preserve log** and enable it if you need to reproduce the issue first.
3. Reproduce the issue.
4. Right-click anywhere inside the console output and choose **Save as...** to export the log to a file, or select the relevant messages and press ``Ctrl+C`` / ``Cmd+C`` to copy them.
5. Paste the copied text into your support email, or attach the saved file.

Safari
------

Safari hides its developer tools by default, so the **Develop** menu needs to be enabled first.

1. Open **Safari** → **Settings** (or **Preferences**) → **Advanced**, and enable **Show features for web developers**.
2. Open the developer tools by pressing ``Cmd+Option+C``, or via **Develop** → **Show JavaScript Console**.
3. Reproduce the issue.
4. Click and drag to select the relevant messages in the console, then press ``Cmd+C`` to copy them. Safari does not offer a built-in "save to file" option, so paste the copied text directly into your support email or a text file.

Mobile Browsers
----------------

Mobile browsers don't expose a console directly. If you're seeing an issue in the :doc:`mobile-app`, the easiest way to capture a console log is to reproduce the issue in the desktop version of the same browser, or use that browser's remote-debugging tools (for example, connecting an Android device to Chrome's ``chrome://inspect`` page, or an iPhone to Safari's Develop menu on a Mac). If that isn't practical, a screen recording of the issue is a good substitute — contact :doc:`support` for guidance.