Skip to main content

Send a browser crash report

By default, an unexpected JavaScript or display error opens Send crash report? so you can review and submit error details to BoatKit support. You can also choose whether this Viewer sends future errors automatically without asking.

Before you start​

Report uploads require you to be signed in to a BoatKit account in the regular browser Viewer. This includes a Viewer connected directly to your boat over the local network. Local-only users without a signed-in BoatKit account, anonymous public views, and marketing replay viewers do not upload reports.

Uploading requires an Internet connection to BoatKit Cloud. Local BoatKit operation continues independently of crash reporting and remains available without an Internet or BoatKit Cloud connection.

Send the current report​

  1. In Send crash report?, expand Error details if you want to review the report.
  2. Leave Automatically send future crash reports without asking unchecked to continue reviewing each report, or check it to enable automatic reporting for this Viewer.
  3. Select Send report, then wait for the result described below. Not now dismisses the dialog without uploading or changing your automatic-report preference.
  4. Close the dialog. If the Viewer shows BoatKit hit a display error, select Reload BoatKit to continue. You can reopen the report dialog with Send crash report on that screen. If the report is pending and browser storage is unavailable, reloading can discard it.

Confirm it is working​

  • Crash report sent. confirms that the report was uploaded to BoatKit Cloud for BoatKit support.
  • Crash report pending. BoatKit will retry when connected. means the report is queued for retry. It does not confirm an upload or guarantee eventual delivery.

Choose automatic reporting​

  1. Open Settings > Preferences > Crash Reports.
  2. Turn Automatically send crash reports on or off.

The setting is off by default and applies to This Viewer. You can also enable it by checking Automatically send future crash reports without asking and selecting Send report in a crash-report dialog. When enabled, future unexpected JavaScript and display errors submit in the background without opening the dialog while you are signed in to a BoatKit account. A failed automatic upload waits for retry without prompting.

Turning it off discards pending automatic reports. A report you requested with Send crash report retains your explicit consent and remains eligible for retry.

What a report contains​

Browser reports include:

  • JavaScript error details and any available JavaScript stack—a trace of the software calls involved in the error.
  • A React component stack, identifying the parts of the display involved, when available.
  • The BoatKit version and build, page path, and browser details.
  • Whether the Viewer connection is local or through BoatKit Cloud, and the vessel identity.

Browser reports do not capture screenshots, full vessel logs, or the contents of the Viewer's data stores.

BoatKit removes URL queries, fragments, and credentials embedded in URLs, and redacts common credential patterns. Arbitrary error text may still contain equipment details, local network addresses, or other sensitive information; redaction is not guaranteed to remove every such detail.

Reports are encrypted in transit to BoatKit Cloud. Uploaded reports are accessible only to BoatKit support administrators in their diagnostics list and become unavailable after 30 days. The account upload limit is five reports per hour.

Offline and pending reports​

Up to five pending reports are held in browser-local storage for at most 24 hours. Retries run while this Viewer is open under the same account and vessel, when the Internet connection and account authorization allow an upload.

If browser storage is blocked or full, only in-memory retry is possible. Reloading can discard the report. A pending report can expire before it is uploaded.

Crash reporting cannot reconstruct an earlier incident that was not captured. It also does not capture a closed tab, a killed browser process, or the operating system terminating the browser because of memory pressure.

If a report cannot be sent​

  • If BoatKit asks you to sign in, check that this regular browser Viewer is signed in to your BoatKit account.
  • If the report remains pending, check your Internet connection and keep this Viewer open under the same account and vessel. The five-reports-per-hour account limit can also delay uploads.
  • For a direct local connection, browser reporting requires an updated vessel runtime. An existing account authorization may also need you to reconnect your BoatKit account once to grant browser-report permission. Newer Viewers retain sign-in to older runtimes using the previous permissions. Automatic retries never open a login window.

If support needs more context, provide the incident time and time zone, the BoatKit version, the action immediately before the error, and whether a device was rebooted.