Setup and Configure Expo EAS CI/CD

[tyrauber]

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]

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

[wipfli]

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

[wipfli]

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

[wipfli]

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?

[KiwiKilian]

What's stoppin us from just building on GH actions like we are doing with the RN app?

[tyrauber]

@KiwiKilian, nothing. It is just easier with EAS. EAS handles signing and installs via QR codes. Would be difficult to replicate that in github actions.

[KiwiKilian]

Ah sure, but just for checking if examples still build we won't need it.