digidem / digidem/comapeo-core-react-native
iOS: TestFlight upload validation as pre-release ritual
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 8h 24m
- Merged PRs (30d)
- 9
Description
TestFlight upload catches a class of distribution-only validation issues — MinimumOSVersion matches across all embedded frameworks, Info.plist schema, signing chain — that local builds and codesign-only CI never surface.
Goal: document a pre-release ritual that uploads the example app to TestFlight (or asserts a successful upload in CI on a release tag) before any version cut. No code change required initially; just a documented checklist + (optionally) an EAS workflow.
Adjacent to #20 (real-device runtime test) but separable — they catch different failure shapes.
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 by locating the example app's release documentation and any existing EAS or CI configuration. Document a pre-release checklist covering a TestFlight upload and the stated validation checks; consider the optional EAS workflow separately. Done means the ritual is clear enough to run before a version cut.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, react-native
- Domain
- documentation, mobile-dev, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100