facebook/react · error · Error
354
354
Error message
getInspectorDataForViewAtPoint() is not available in production.
What it means
The RN Inspector's getInspectorDataForViewAtPoint depends on dev-only renderer hooks (findNodeHandle/inspect internals) that are compiled out of production bundles; when the surrounding dev-tooling branch is absent, calling it throws. It is a tooling API, not an application API - production builds intentionally have no inspector.
Source
Thrown at packages/react-native-renderer/src/ReactNativeFiberInspector.js:196
...inspectorData,
pointerY: locationY,
frame: {left: pageX, top: pageY, width, height},
touchedViewTag: nativeViewTag,
closestPublicInstance,
});
},
);
},
);
} else {
console.error(
'getInspectorDataForViewAtPoint expects to receive a host component',
);
return;
}
} else {
throw new Error(
'getInspectorDataForViewAtPoint() is not available in production.',
);
}
}
export {getInspectorDataForInstance, getInspectorDataForViewAtPoint};
View on GitHub (pinned to eafeac097b)
Solutions
- Gate every call with if (__DEV__).
- Run inspection only against dev/debug builds.
- Strip inspector imports from release entry points (Metro transformer / babel plugin) so they are dead-code eliminated.
Example fix
// before
const data = getInspectorDataForViewAtPoint(x, y, callback);
// after
if (__DEV__) {
getInspectorDataForViewAtPoint(x, y, callback);
} Defensive patterns
Strategy: validation
Validate before calling
if (__DEV__) {
getInspectorDataForViewAtPoint(x, y, callback);
} else {
// inspection is not available in production; skip or degrade gracefully
} Type guard
const canInspect = () => Boolean(__DEV__);
Prevention
- Gate all inspector calls with __DEV__.
- Use dev builds for inspection workflows.
- Strip inspector imports from release entry points so they are dead-code eliminated.
When it happens
Trigger: Calling getInspectorDataForViewAtPoint (directly or through inspector/overlay libraries) in a production RN bundle where __DEV__ is false and the dev-only machinery is stripped.
Common situations: Dev-only inspector integrations left enabled in release builds; QA/overlay tooling that assumes the inspector exists everywhere; libraries calling renderer internals without a __DEV__ guard.
Related errors
- isChildPublicInstance() is not available in production.
- Could not find host instance from fiber
- 559
- Hooks not supported by this renderer
- React is running in production mode, but dead code eliminati
AI-assisted analysis of facebook/react@eafeac097b (2026-08-21).
Data as JSON: /api/errors/648b372ef5577e33.
Report an issue: GitHub.