Actions
Feature #70
open
VJ
Add explicit EAS build scripts for the client app
Feature #70:
Add explicit EAS build scripts for the client app
Status:
To Do
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Imported from GitHub issue 211.
Source labels: ready-for-agent.
Original state: open. No source milestone.
What to build¶
Add an explicit, reproducible command interface for triggering EAS cloud builds for the client app. Provide platform-and-profile-specific scripts for Android and iOS across the existing development, preview, and production profiles, plus convenient root-level shortcuts for the commonly used preview and production builds. Pin EAS CLI as a development dependency so commands do not depend on a globally installed version.
Keep local native build commands distinct from EAS cloud builds. CI automation, EAS Submit, and non-interactive credential setup are outside this issue.
Acceptance criteria¶
- The client workspace exposes explicit EAS cloud-build scripts for Android and iOS using each existing
development,preview, andproductionprofile. - The repository root exposes shortcuts for Android and iOS preview and production builds.
- Script names clearly distinguish EAS cloud builds from existing local Android build scripts.
- EAS CLI is pinned to an exact development-dependency version and the workspace lockfile is updated.
- Each command runs from the client app directory and resolves the intended platform and build profile.
- Authentication requirements and expected development, preview, and production artifacts are documented for contributors.
- Verification does not start a billable remote build.
- CI build automation, EAS Submit, and non-interactive credential configuration remain out of scope.
Blocked by¶
None - can start immediately.
No data to display
Actions