Edit this page
Learn how to submit your app to the Apple App Store from your computer and CI.
This guide outlines how to submit your app to the Apple App Store from your own computer and from CI.
-
npm install -g eas-cli && eas login
1
You'll need a native app binary signed for store submission. You can either use EAS Build or do it on your own.
2
To submit the binary to the App Store, run eas submit -p ios
from inside your project directory. The command will lead you step by step through the process of submitting the app. See the Configuration with eas.json page to learn how to pre-configure your submission.
Although it's possible to upload any binary to the store, each submission is associated with an Expo project. That's why it's important to start a submission from inside your project's directory because app config is defined inside that directory.
If you have not generated an App Store Connect API Key yet, you can let EAS CLI take care of that for you by signing into your Apple Developer Program account and following the prompts. You can also upload your own API Key or pass in an Apple app-specific password.
To upload your iOS app to the Apple App Store, run eas submit --platform ios
and follow the instructions on the screen.
The command will perform the following steps:
Log in to your Expo account and ensure that your app project exists on EAS servers.
Ensure that your app exists on App Store Connect and its Bundle Identifier is registered on Apple Developer Portal:
You will be asked to log in to your Apple Developer account and select your team. You can also provide this information in eas.json by setting appleId
and appleTeamId
in the submit profile. The Apple ID password has to be set with the EXPO_APPLE_PASSWORD
environment variable.
The command will look for ios.bundleIdentifier
in the app config.
If you are submitting your app for the first time, it will be automatically created.
Unless expo.name
in your app configuration is found or appName
is provided in eas.json, you will be prompted for the app name.
You can also specify your app's language and SKU using language
and sku
keys in eas.json. If you have never submitted any app before, you may also have to specify your company name with companyName
.
If you already have an App Store Connect app, this step can be skipped by providing the
ascAppId
in the submit profile. The ASC App ID can be found either on App Store Connect, or later during this command in the Submission Summary table.
Ensure you have the proper credentials set up. If none can be found, you can let EAS CLI set some up for you.
App Store Connect API Key: Create your own API Key then set it with the ascApiKeyPath
, ascApiKeyIssuerId
, and ascApiKeyId
fields in eas.json.
App Specific Password: Provide your password and Apple ID Username by passing them in with the EXPO_APPLE_APP_SPECIFIC_PASSWORD
environment variable and appleId
field in eas.json, respectively.
Ask for which binary to submit. You can select one of the following:
The latest successful iOS build for the project on EAS servers.
Specific build ID. It can be found on the builds dashboard.
Path to an .ipa archive on your local filesystem.
URL to the app archive.
This step can be skipped if one of the following CLI parameters is provided:
--latest
,--id
,--path
, or--url
.
A summary of the provided configuration is displayed and the submission process begins. The submission progress is displayed on the screen.
Your build should now be visible on App Store Connect. If something goes wrong, an appropriate message is displayed on the screen.
The eas submit
command is able to perform submissions from a CI environment. All you have to do is ensure that all required information is provided with eas.json and environment variables.
You must do the following:
Provide the archive source (--latest
, --id
, --path
, or --url
).
Make sure that the iOS Bundle Identifier is present in your app config file.
Set the ASC App ID (ascAppId
in eas.json). The ASC App ID is required to skip the Apple Developer log-in process, which will likely not be possible on CI due to the 2FA prompt.
Set up your App Store Connect API Key with EAS Servers. You can check the state of your credentials by running eas credentials
or by running eas submit -p ios
interactively.
App Store Connect API Key: Create your own API Key then set it with the ascApiKeyPath
, ascApiKeyIssuerId
, and ascApiKeyId
fields in eas.json.
App Specific Password: Provide your password and Apple ID Username by passing them in with the EXPO_APPLE_APP_SPECIFIC_PASSWORD
environment variable and appleId
field in eas.json, respectively.
Example usage:
-
eas submit -p ios --latest --profile foobar
If you ever need to submit your build without going through EAS Submit, for example, if the service is temporarily unavailable for maintenance, you can upload to the Apple App Store manually from a macOS device.
Start by creating an app profile in App Store Connect, if you haven't already:
Finally, you need to upload the IPA to the Apple App Store.
This process can take a few minutes, then another 10-15 minutes of processing on Apple's servers. Afterward, you can check the status of your binary in App Store Connect:
To learn how to automatically submit your app after a successful build, refer to the Automating submissions.