Skip to content
Toado Docs

Extension troubleshooting

If the extension is misbehaving, walk this list before contacting support. Most issues have a five-second fix.

Extension icon is grayed out

You are on a URL Chrome blocks for extensions: chrome://, chrome-extension://, the Chrome Web Store, view-source:. Navigate to a normal http:// or https:// page and the icon re-enables.

Click does nothing

  • Check the icon is enabled for this site (no orange warning dot in the corner).
  • Make sure you are signed in. Click the icon and look for a sign-in prompt.
  • Reload the tab and try again. If the page loaded before the extension activated, the content scripts may not be injected yet.

”Capture failed” toast

Common causes:

  • API unreachable: the toast offers a retry. Failed retries fall back to the offline queue.
  • Auth expired: sign back in via the extension popup. The capture is queued for retry after auth.
  • The tab navigated mid-capture: the service worker aborts and retries once. If both attempts straddle navigation, you see the failure toast.

Console / network capture is empty on a specific site

Most often, the site has a strict Content Security Policy that blocks injected scripts. The capture metadata flags this, and the ticket gets a banner: “Console capture unavailable on this page (CSP).”

The screenshot, URL, and (usually) network capture still work. The ticket is still useful; it is just lighter on the DevTools side.

Captures only show the top frame

By design in v1. Cross-origin iframes are sandboxed by the browser; the extension’s content script runs in every frame, but cross-origin frame contents are out of scope for v1. Top-frame console and network are captured.

Sign-in loop

You click sign-in, the tab opens, you sign in, the tab closes, but the extension still asks you to sign in.

  • Cookies blocked: the sign-in handoff uses session cookies. If your browser or an extension blocks third-party cookies for app.toado.dev, the handoff fails. Allow cookies for that origin.
  • Multiple Chrome profiles: ensure the sign-in tab opens in the same profile the extension is installed in.
  • Hard reset: in the extension popup, Sign out, then Sign in again.

The popup is blank

Hard-refresh the popup: right-click the extension icon › Inspect popup, then in the DevTools window, Cmd+Shift+R. If the popup still loads blank, reinstall the extension.

Captures are stuck in the offline queue

Open the extension options, Queue tab. Each stuck capture has a status. Common reasons:

  • Forbidden: the queued capture targets a project the current user no longer has access to (signed in as a different account, project deleted, etc.). Discard the capture or sign back in as the original account.
  • Validation error: rare; usually a payload problem. Discard.
  • Quota exceeded (429): wait, then click Submit now. Bulk-submit fewer at a time if needed.

Keyboard shortcut does not fire

  • Confirm the shortcut is set in chrome://extensions/shortcuts. Some Chrome installs lose them.
  • Confirm no other extension or system app has the same shortcut.
  • On Windows, some keyboards (especially gaming keyboards) intercept Alt-key combos in OS-level macros. Test with a different key combination.

Heavy memory or CPU usage

The extension’s content scripts buffer console and network activity per-tab. On long-lived tabs with very chatty pages (heavy logging or hundreds of network requests), the buffer grows. Close and reopen the tab to reset, or set a stricter limit in Options › Capture.

Where to ask

If none of the above resolves it, get in touch. Include:

  • Chrome version (chrome://version).
  • Operating system and version.
  • Extension version (footer of the options page).
  • A brief description of what you did and what you saw.

A capture from the extension itself (yes, you can capture the Toado options page) is the fastest possible report.