|
| 1 | +# Mobile build readiness |
| 2 | + |
| 3 | +This checklist covers the Expo companion in `apps/mobile`. It does not cover |
| 4 | +the native Chromium build in `apps/android-engine`. |
| 5 | + |
| 6 | +## Local toolchain |
| 7 | + |
| 8 | +- Node.js 24 (see the repository `.nvmrc` and root `engines` field) |
| 9 | +- pnpm 9.12.0 via Corepack |
| 10 | + |
| 11 | +Run these local release-readiness checks from the repository root: |
| 12 | + |
| 13 | +```bash |
| 14 | +corepack enable |
| 15 | +pnpm install --frozen-lockfile |
| 16 | +pnpm --filter @tronbrowser/mobile typecheck |
| 17 | +pnpm --filter @tronbrowser/mobile lint |
| 18 | +pnpm --filter @tronbrowser/mobile test |
| 19 | +pnpm --filter @tronbrowser/mobile export |
| 20 | +cd apps/mobile && pnpm dlx expo-doctor |
| 21 | +``` |
| 22 | + |
| 23 | +The mobile package intentionally stays on the workspace TypeScript 5.x line. |
| 24 | +Expo Doctor currently recommends TypeScript 6 for SDK 57, but changing the |
| 25 | +compiler major is a workspace-wide migration rather than a mobile-only update. |
| 26 | +The exception is declared in `package.json`; typecheck, tests, lint, and both |
| 27 | +platform bundles remain the CI acceptance checks. Expo Doctor is a |
| 28 | +network-backed local diagnostic and is not run in CI. |
| 29 | + |
| 30 | +## EAS preview build |
| 31 | + |
| 32 | +The app is linked to the `profullstack/tronbrowserdev` EAS project. Cloud builds |
| 33 | +require an Expo access token from the `profullstack` account. The account owner |
| 34 | +should add that token directly to the GitHub repository as the `EXPO_TOKEN` |
| 35 | +Actions secret; the token should not be shared in chat or committed to git. |
| 36 | + |
| 37 | +After the secret is present, run the `Mobile` workflow manually with: |
| 38 | + |
| 39 | +- platform: `android` |
| 40 | +- profile: `preview` |
| 41 | +- submit: `false` |
| 42 | + |
| 43 | +The workflow starts an asynchronous EAS build. Its EAS build URL is the handoff |
| 44 | +artifact for review. Store submission remains a separate production step and |
| 45 | +requires the corresponding Apple or Google developer account and signing setup. |
0 commit comments