TL;DR: Use the update command directly in your route handler or nav event: Intercom('update', {"hide_default_launcher": true}) to hide, and Intercom('update', {"hide_default_launcher": false}) when you navigate back to a page that should show it. Skip the dashboard page-targeting for SPAs, it only fires on full page loads. The accepted answer confirms this exact technique worked in an Angular SPA to hide the launcher on screens where it covered buttons.

## Fix
1. Use the update command directly in your route handler or nav event: Intercom('update', {"hide_default_launcher": true}) to hide, and Intercom('update', {"hide_default_launcher": false}) when you navigate back to a page that should show it.
   Expected: the request routes instead of erroring.
2. You can also pass hide_default_launcher in the boot settings if a whole section of the app never needs it.
   Expected: this specific failure stops.

## Details
Skip the dashboard page-targeting for SPAs, it only fires on full page loads. The accepted answer confirms this exact technique worked in an Angular SPA to hide the launcher on screens where it covered buttons. Context: Stack Overflow #57388730 (accepted answer, 34 votes): Single-page app loads Intercom by default, but the dashboard's page-targeting for hiding the widget does not work in SPAs since there are no real page loads. Reporter wanted to hide the launcher on specific screens where it was obscuring buttons, without manually hiding the DOM node.

## When to use
You hit exactly this: Hide the Intercom launcher on specific SPA pages with hide_default_launcher in Hide.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Hide.