nadavWeisler / nadavWeisler/MedCodeTranslator
[CI] Publish first public iOS build path from EAS workflow
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 7m
- Merged PRs (30d)
- 7
Description
Problem summary
Mobile store publishing is listed as backlog in CONTRIBUTING.md. Issue #29 (mobile deployment workflow) is closed, but there is no documented path to a first public iOS build via EAS.
Affected area
- EAS / Expo build configuration
app.config.ts- CI workflows
store-listing.md,docs/APP_STORE_DESCRIPTION.md
Expected behavior
A repeatable, documented workflow produces a testable iOS build (TestFlight or equivalent) from the repo.
Acceptance criteria
- EAS iOS build workflow is documented step-by-step.
- Required secrets and Apple credentials are listed (not committed).
- First internal or TestFlight build is produced or build instructions verified on CI.
-
store-listing.mdaligns with the shipped build configuration.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with CONTRIBUTING.md and app.config.ts, then inspect the CI workflows and the existing store-listing.md and docs/APP_STORE_DESCRIPTION.md files. Document the EAS iOS build steps, required uncommitted secrets and Apple credentials, and verify that the instructions produce or support a first internal or TestFlight build with matching store information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, devops, documentation, mobile, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100