I scanned 23 open‑source Expo apps before they hit the App Store. Here’s what a pre‑flight check caught.
Описание и применение
Экспо‑разработчики часто сталкиваются с ошибками сборки и отклонением приложений в App Store из‑за конфигурационных ошибок. Автор создал CLI‑утилиту expo‑preflight, которая статически анализирует файлы конфигурации и выявляет 13 реальных проблем в 23 популярных репозиториях, уменьшая количество ложных срабатываний с 83 до 29.
Задача
Expo builds and store reviews often fail due to configuration errors that are hard to detect manually.
Результат
The tool reduced reported errors from 83 to 29 after fixes, uncovered 13 real configuration problems, and demonstrated the value of automated cross‑file consistency checks.
Рабочий процесс
- Clone each repository
- Run
npx expo-preflight - Review the generated report
- Fix identified issues
- Re‑run the tool to confirm resolution
Доказательства
I built a small CLI to do it, and then pointed it at real apps to see whether the problems are real.
It reads app.json / app.config.*, package.json, eas.json and .gitignore, never runs your app and never prints secret values.
My first run produced 36 errors and 56 warnings, and roughly half were wrong.
Missing iOS usage strings (4 of the 6 apps with expo-image-picker or expo-media-library installed).
A tracked .env in git (2 of 23 apps).
Update channels that don't exist (2 of the 6 apps with both expo-updates and an eas.json).
- Дата записи: 2026-10-05T13:55:53.539Z