Learn about different options for supplying your app signing credentials to EAS Build.

Edit this page

---

EAS Build gives you two options for how you can supply your build jobs with app signing credentials:

1. Automatically managed credentials: EAS can host your app signing credentials and take care of sharing them with teammates that have the necessary permissions.
2. Local credentials: You create a credentials.json file in your project that points to your keystore (Android) and/or provisioning profile and distribution certificate (iOS), along with associated passwords. This is uploaded from your local machine at the time any given build job is run, and disposed of once that build job has completed.

Regardless of which option you choose, your first step for using your existing set of credentials is to set them up as local credentials in credentials.json. Refer to the credentials.json section of the local credentials guide for more information on how to do this.

Once your credentials.json file is configured, you can run eas credentials, choose a platform, and then select "Update credentials on Expo servers with values from credentials.json" to upload them to be hosted and managed by EAS, if you would like. Read more about syncing credentials.