Import an existing Expo app

Steps

1. On the dashboard, choose Import an existing Expo app.
2. Choose or drop the .zip. Nothing in it is run.
3. Read the report: To fix before importing, Good to know and Done for you.
4. Wait for the preview, check the name, Android package and iOS bundle ID, then choose Import app. If the preview did not start (often missing EXPO_PUBLIC_* values), choose Import anyway.

Limits

• One Expo Router app per .zip, up to 100 MB.
• Up to 2,000 files, 8 MB of code and text, and 25 MB of media (10 MB per file).
• Refused: monorepos, local-folder or git dependencies, apps without Expo Router, hand-written code in android/ or ios/, and an app.config.* that runs code (a plain one becomes app.json).
• Left out: node_modules, .git, build output, generated native folders, signing files and unused media.

After the import

• The upload is version one; anything Done for you changed is a second version you can undo. Moving the app to FluxNative's Expo SDK can touch config and layout files, not only package.json (such as app.json or app/_layout.tsx); Version history shows exactly what changed.
• .env, .env.local and .env.production merge into the app's .env. Move server keys to Server › API keys & secrets.
• If the preview or checks still fail, the chat offers a compatibility pass: the smallest fix (at most 5 files and 60 lines), usually 20–70 credits. Keep or undo it.

Related

Connect an editor · Export the project