Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup and Configure Expo EAS CI/CD #337

Open
tyrauber opened this issue Apr 24, 2024 · 4 comments
Open

Setup and Configure Expo EAS CI/CD #337

tyrauber opened this issue Apr 24, 2024 · 4 comments
Assignees

Comments

@tyrauber
Copy link
Collaborator

tyrauber commented Apr 24, 2024

In order to use Expo and EAS to build the iOS and Android app, as setup in the feat/expo branch, 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.

@wipfli
Copy link

wipfli commented Apr 28, 2024

@louwers can we use the same Apple account as we use in MapLibre Native?

@wipfli
Copy link

wipfli commented Apr 28, 2024

How much is one EAS build, how many builds do we expect per month?

@wipfli
Copy link

wipfli commented Apr 28, 2024

@louwers can you create an Expo EAS account and store the credentials in our password manager?

@wipfli
Copy link

wipfli commented Apr 28, 2024

If we need to store a token for some actions, we can store it in the global maplibre github org and share it with individual projects, or we can store it in projects directly. What do you think makes more sense here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants