Build your apps with EAS, without using EAS
The app is based on the tabs template, just as example.
The workflow is a simple GitHub Actions workflow using expo-github-action, eas build --local command, and uploading artifacts to the workflow run.
By default, the workflow is only running when you trigger it manually. But you can customize it however you like. Just make sure you are running the eas build --local command with the right --platform and --profile flags.
Ubuntu is the fastest environment of GitHub Actions, but to support iOS builds we need to use macOS. You can optimize this by changing the OS per platform.
Right now, the local app binary has a name with a colon. actions/upload-artifact doesn't accept colon in files, so we need to rename it before uploading. (more info here)
As of writing, the eas build --local command can only build a single platform per execution. You can run it multiple times in your workflow, but only for a single platform per run.
If you want to fully disconnect from Expo services, you'll need to maintain the keystore or certificates yourself. You can do that by configure EAS with local credentials. When your CI provider doesn't allow you to add "secret files", like GitHub Actions, you can encode these files to base64 strings and decode whenever you need it.
It's highly recommended to keep keystores and certificates out of your repository to avoid security issues.
with :heart: byCedric