A Flow Lab demo built without a client: a sample report on a fictional project, FieldCrew. You get the same kind of report for your app. An audit of an Expo or React Native app costs $100 and takes 1 business day. How it was built and what it costs

App store release readiness audit: FieldCrew

Stack: Expo ~53.0.9 · React Native 0.79.2 · TypeScript · tests: 0 · lockfile: yarn.lock

iOS bundle ID: com.example.fieldcrew · Android package: com.example.fieldcrew

3 required before release · 10 to fix · 3 notes. The audit needs only the project files: nothing is installed or run.

LevelAreaFindingFix
🔴StackThe project uses Expo SDK 53, while the current SDK is 57, four versions newer. Stores now require recent versions of Xcode and the iOS SDK and a recent Android target API level. Older Expo SDKs usually cannot meet these requirements.Upgrade the SDK step by step from 53 to 57, fix breaking changes, and retest the app.
🔴SecurityThe project contains a .env file, and .gitignore has no rule yet that keeps such files out of the repository.Remove the .env file from the repository, rotate the keys, and add .env* to .gitignore.
🔴Securitysrc/billing/config.ts appears to contain a Stripe live secret key.Move it to the server or EAS secrets and rotate it. Anyone can read anything inside the app bundle.
🟡ConfigThe iOS bundle identifier "com.example.fieldcrew" looks like a placeholder.Choose the final bundle ID before the first store upload: after that, it stays with the app permanently.
🟡ConfigThe Android package "com.example.fieldcrew" looks like a placeholder.Choose the final package name before the first store upload: after that, it stays with the app permanently.
🟡BuildThe project has no eas.json file yet, so cloud builds are not set up.Add EAS build profiles for development, preview, and production.
🟡App StoreThe icon is 512×512 pixels, and the App Store requires 1024×1024.Export the icon at 1024×1024.
🟡App StoreThe icon PNG has transparency, and App Store icons must be opaque.Place the icon on a solid background.
🟡Google PlayThe Android adaptive icon is not set up yet.Add adaptiveIcon with a foreground image and a background color.
🟡App StoreApp Store Connect asks about export compliance (encryption) with every upload, and the answer is not in the app config yet.Set ios.config.usesNonExemptEncryption (usually false for HTTPS-only apps).
🟡App StoreThe app uses expo-camera, and its iOS camera permission text (NSCameraUsageDescription) is not set yet. The App Store often rejects apps with generic default permission texts (guideline 5.1.1).Write a specific explanation of why the app needs each permission.
🟡App StoreThe app uses expo-location, and its iOS location permission text (NSLocationWhenInUseUsageDescription) is not set yet. The App Store often rejects apps with generic default permission texts (guideline 5.1.1).Write a specific explanation of why the app needs each permission.
🟡SecurityEverything in the "extra" section of the app config ships inside the app. This section currently holds supabaseServiceKey.Keep only public values in extra.
⚪BuildWhen dependencies are installed, the postinstall script runs "patch-package," a widely used tool.
⚪App StoreExpo adds privacy manifests for its own modules, and the app's own privacy manifest is not filled in yet.Declare in it any data collection and any APIs that Apple requires a reason for, if the app or its third-party libraries use them.
⚪QualityThe audit found no automated tests in the project.Add tests for the key logic before making changes.

Estimated work to a store-ready build: about 21 hours (the fixes above, EAS setup, and first builds). Store accounts (Apple Developer, Google Play) stay with the owner, and the app is published from the owner's accounts.

Plan, step by step

  1. First, remove keys and secrets from the code and repository and rotate them.
  2. Upgrade Expo SDK and dependencies, fix breaking changes, and retest the app.
  3. Work through the "To fix" items: permission texts, icons, encryption, build settings.
  4. Set up EAS cloud builds and make test builds for iOS and Android.
  5. Testing on your devices: TestFlight (iOS) and internal testing (Google Play).
  6. Submission for App Store and Google Play review from your accounts, plus answers to reviewer feedback.