nadavWeisler / nadavWeisler/MedCodeTranslator
[CI] Publish first public Android 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
Android publishing path is not documented or automated end-to-end. CONTRIBUTING.md lists a first public Android build as backlog work.
Affected area
- EAS / Expo build configuration
app.config.ts- CI workflows
store-listing.md
Expected behavior
A repeatable, documented workflow produces a testable Android build (internal track or Play Console upload).
Acceptance criteria
- EAS Android build workflow is documented step-by-step.
- Required secrets and Play Console setup are listed (not committed).
- First internal build is produced or build instructions verified.
- Adaptive icon and splash assets meet Play Store requirements.
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, app.config.ts, the existing CI workflows, and store-listing.md to trace the intended Android release path. Review the EAS/Expo build configuration and document the required secrets and Play Console setup without committing them. Done means the workflow is reproducible, the assets meet Play Store requirements, and a first internal build is produced or the instructions are verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions, typescript
- Domain
- 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