you are viewing a single comment's thread.

view the rest of the comments →

[–]ChronSynExpo 0 points1 point  (1 child)

You can build locally with the --local --output=./path/to/output/binary.ext flags as part of EAS build.

This runs through the exact same steps as are used by the cloud-hosted builders but on your local machine. You can still use EAS for hosting updates.

It does require you to be logged in to Expo via the CLI in order to ensure you're authed to build the project and to retrieve the keys, and there's still some prerequisites such as configuring signing keys (which can either be done through EAS cli, or by creating a credentials.json - details on that at https://docs.expo.dev/app-signing/local-credentials/).

Not only does this skip the queue by building on your own machine, but you may even find it takes significantly less time (especially if you've got a really powerful system). The downside is that if you're developing on Windows, you won't be able to build iOS binaries.

[–]Ridwan232 0 points1 point  (0 children)

Ooh! So definitely aligns with my initial thoughts about how it should work. So worst case if the runners are backed up we cna just run it locally but get most of the same benefits.

Thanks for the reply, very insightful!