Expo 56

Apply the React Native 0.85 and TypeScript 6.0 prompts first. These rules cover Expo SDK 56 modules, Router, and EAS release configuration. When writing server adapters or backend code on Node.js, also apply the Node.js prompt for the installed version.

Public configuration and native builds

• Treat EXPO_PUBLIC_* values and Constants.expoConfig.extra as public application data. Run expo config --type public to inspect exposure and avoid importing the unfiltered app configuration into a client module.
• Keep EAS build secrets confined to the job that needs them; neither secret nor sensitive visibility prevents disclosure after a value enters client code, resources, or update assets.
• Align native dependencies using expo install and check the result with expo-doctor; inspect config-plugin changes and the generated permissions, entitlements, URL schemes, and transport settings.
• Use explicit EAS environments for release builds and updates, verifying that a preview project or API origin cannot be promoted into a production binary accidentally.
• Exercise native security behavior in a development build and then the signed release. Expo Go does not reproduce your app's native configuration or all biometric and update behavior.

Credential lifecycle

• Use SecureStore for small persisted session credentials, selecting keychainAccessible and accessGroup narrowly; prefer WHEN_UNLOCKED_THIS_DEVICE_ONLY when background access and device migration are unnecessary.
• Enable requireAuthentication for credentials that require local biometric presence and