App does not request all permissions immediately on first launch

Requesting camera, location, and notification permissions simultaneously on first launch is one of Apple's most-cited rejection reasons under guideline 5.1.1 (data collection and storage). Users who see a permission flood immediately deny everything, and reviewers interpret it as a sign the developer hasn't thought about why each permission is actually needed. More practically: a user who denies all permissions on first launch may never see the feature that needs them, making the permission useless. Contextual permission requests — asked at the moment the feature is first triggered — produce dramatically higher grant rates and clearer justification.

Move each permission request to the exact moment the user first triggers the feature that needs it — not in App.tsx on mount.

// src/screens/CameraScreen.tsx
async function handleTakePhoto() {
  const { status } = await Camera.requestCameraPermissionsAsync();
  if (status !== 'granted') {
    Alert.alert('Camera access needed', 'Please enable camera access in Settings to take photos.');
    return;
  }
  // proceed with camera
}

For notifications, add a pre-permission screen explaining the value ("Get alerts when your order ships") before calling requestPermissionsAsync(). Never fire multiple permission requests in parallel with Promise.all().