maplibre / maplibre/maplibre-react-native
Setup and Configure Expo EAS CI/CD
- Dominant language
- TypeScript
- Stars
- 661
- Forks
- 124
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 30
Description
In order to use Expo and EAS to build the iOS and Android app, as setup in [the feat/expo branch](https://github.com/maplibre/maplibre-react-native/pull/162), we need two things:
- For IOS, we need a valid iOS app bundle identifier (this requires an Apple Developer account)
- An Expo EAS account for Key Management
If we have these two things, we can use the eas cli tools to manage building the iOS and Android App. We can either use the EAS build services (paid building based on usage) or use the eas cli tools in github actions to build. The second option is free, but is much more difficult to share and review builds. EAS allows you to test builds by scanning a QR code, making PR reviews much easier. Regardless, an Expo EAS account is required to use the eas cli because it handles all the iOS and Android app credentials for us.
An [Expo EAS account can be created here](https://expo.dev/signup).
Contributor guide
Research direction
Start by reviewing the feat/expo branch in PR #162 and the EAS CLI and GitHub Actions options described here. Confirm the required iOS bundle identifier and Expo EAS account, then establish one agreed build path for both iOS and Android and verify that builds can be produced and shared for PR review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions, ios, react-native
- Domain
- build-system, ci-cd, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100