facebook/react · error · Error

overrideError not supported by this renderer

Error message

overrideError not supported by this renderer

What it means

The legacy renderer adapter stubs overrideError as a throwing no-op. The 'force error boundary' debug toggle works by flipping fiber error-boundary state via the v16+ reconciler instrumentation; React 15's stack reconciler has no such mechanism, so the backend refuses the command.

Source

Thrown at packages/react-devtools-shared/src/backend/legacy/renderer.js:1201

      }
    }
  }

  // v16+ only features
  const getProfilingData = () => {
    throw new Error('getProfilingData not supported by this renderer');
  };
  const handleCommitFiberRoot = () => {
    throw new Error('handleCommitFiberRoot not supported by this renderer');
  };
  const handleCommitFiberUnmount = () => {
    throw new Error('handleCommitFiberUnmount not supported by this renderer');
  };
  const handlePostCommitFiberRoot = () => {
    throw new Error('handlePostCommitFiberRoot not supported by this renderer');
  };
  const overrideError = () => {
    throw new Error('overrideError not supported by this renderer');
  };
  const overrideSuspense = () => {
    throw new Error('overrideSuspense not supported by this renderer');
  };
  const overrideSuspenseMilestone = () => {
    throw new Error('overrideSuspenseMilestone not supported by this renderer');
  };
  const startProfiling = () => {
    // Do not throw, since this would break a multi-root scenario where v15 and v16 were both present.
  };
  const stopProfiling = () => {
    // Do not throw, since this would break a multi-root scenario where v15 and v16 were both present.
  };

  function getBestMatchForTrackedPath(): PathMatch | null {
    // Not implemented.
    return null;
  }

View on GitHub (pinned to eafeac097b)

Solutions

  1. Do not use the error-boundary debug toggle on v15 roots — the feature requires fiber.
  2. Upgrade the inspected app to React 16.8+.
  3. Update DevTools so error-override controls are hidden for legacy build types.
  4. For embedders: check renderer.findFiberByHostInstance before sending 'overrideError'.

Example fix

// before
bridge.send('overrideError', {id, rendererID, isForceEnabled});

// after
if (typeof renderer.findFiberByHostInstance === 'function') {
  bridge.send('overrideError', {id, rendererID, isForceEnabled});
}
Defensive patterns

Strategy: validation

Validate before calling

const isFiberRenderer = renderer =>
  typeof renderer.findFiberByHostInstance === 'function';
if (isFiberRenderer(renderer)) {
  bridge.send('overrideError', {id, rendererID, isForceEnabled});
}

Type guard

function isFiberRenderer(renderer) {
  return typeof renderer.findFiberByHostInstance === 'function';
}

Try / catch

try {
  bridge.send('overrideError', {id, rendererID, isForceEnabled});
} catch (error) {
  if (/not supported by this renderer/.test(error.message)) return;
  throw error;
}

Prevention

When it happens

Trigger: The DevTools frontend sends the 'overrideError' message — triggered by the debug-panel action that forces an error boundary to show its fallback (or a component to error) — for a component whose renderer is the legacy (v15) adapter.

Common situations: Using DevTools debug toggles on a React 15 app; mixed v15/v16 multi-root apps where a legacy root is selected; frontend/backend version skew that leaves the toggle enabled for 'outdated' build types.

Related errors

AI-assisted analysis of facebook/react@eafeac097b (2026-08-21). Data as JSON: /api/errors/662fd09302b88928. Report an issue: GitHub.