All in-app links, buttons, and navigation paths lead to real content

Dead-end screens are a leading cause of App Store rejection under Apple's guideline 2.1 (completeness). Reviewers systematically navigate every registered tab and screen — a blank render or immediate crash on any reachable route results in an automatic reject. ISO 25010:2011 functional-completeness defines this failure directly: functionality that exists in the navigator but cannot be used provides zero functional value and destroys reviewer trust, putting the entire binary at risk regardless of how polished the rest of the app is.

Audit every screen registered in your navigator before submission. Remove or replace any that render null or an empty <View />.

// app/(tabs)/settings.tsx — replace null renders with real content
export default function SettingsScreen() {
  // Was: return null;
  return (
    <View style={styles.container}>
      <Text>Settings coming in v2</Text>
    </View>
  );
}

For screens not ready for launch, remove them from the navigator file entirely rather than leaving them registered. A tab that doesn't exist beats a tab that crashes.