App gracefully restores state from storage on launch

An app that crashes or resets to empty state when encountering corrupted or missing persisted data — a realistic scenario after OS updates, storage migrations, or unexpected terminations — forces users into a hard logout or blank screen. CWE-755 (Improper Handling of Exceptional Conditions) applies directly: failing to catch parse errors on startup is a class of unhandled exception that destroys user sessions. ISO 25010:2011 reliability.recoverability requires a defined degradation path when restore fails. The business impact is measurable: every startup crash from a missing try/catch translates to an uninstall.

Wrap all startup storage reads in try/catch and always fall through to a safe default state. Show a splash screen until restoration completes so the UI never renders against partially-loaded state.

import { useEffect, useState } from 'react';
import AsyncStorage from '@react-native-async-storage/async-storage';

export function App() {
  const [ready, setReady] = useState(false);
  const [restoredState, setRestoredState] = useState(null);

  useEffect(() => {
    (async () => {
      try {
        const raw = await AsyncStorage.getItem('appState');
        if (raw) setRestoredState(JSON.parse(raw));
      } catch {
        // Corrupted storage — continue with defaults
      } finally {
        setReady(true);
      }
    })();
  }, []);

  if (!ready) return <SplashScreen />;
  return <AppNavigation initialState={restoredState} />;
}

Restore at least two state categories (auth + navigation) and verify the fallback branch by deliberately corrupting storage in a test device run.