All navigable screens are properly registered in navigation stack/tab/drawer definitions

A screen that appears in the linking config but is not registered as <Stack.Screen> or <Tab.Screen> is a dangling reference — React Navigation logs a warning and refuses to navigate, so deep links, push-notification taps, and navigation.navigate('X') calls silently fail. Orphaned registrations with undefined components crash the tree on mount. The user sees a frozen button, a broken link, or a white screen with no recovery path.

Register every screen named in the linking config inside the matching navigator. In your root navigator file, mirror each config.screens entry with a <Stack.Screen> using the exact same name:

<Stack.Navigator>
  <Stack.Screen name="Home" component={HomeScreen} />
  <Stack.Screen name="ProductDetail" component={ProductDetailScreen} />
</Stack.Navigator>

Run a grep across the codebase for each screen name in linking.config.screens and confirm a component is bound.