EAS Submit

Learn store submission with EAS Submit.

What is EAS Submit?

EAS Submit is the service that sends a built app to the stores. It works separately for Google Play Store and Apple App Store. You start it with eas submit --platform android.

Submission needs store account details: a service account JSON key for Android, an App Store Connect API key for iOS. These are held in the "submit" section of eas.json. EAS Submit also handles signing and version checks; it cuts down manual upload steps.

The submit section

The "submit" section in eas.json holds the store credentials. Android uses "serviceAccountKeyPath", iOS uses "ascApiKeyPath". Paths are relative to the project root.

Example: "submit": { "production": { "android": { "serviceAccountKeyPath": "./keys/play.json" } } } }. Never leave key files in a public folder; add them to .gitignore. You can also pass credentials through environment variables; this separates file paths from code.

Exercise Add the submit profile

Add a "submit" section to the eas.json skeleton. Inside it have a "production" profile. This profile carries an "android" object and a "serviceAccountKeyPath" field.

Show example solution

{
  "build": {
    "preview": { "android": { "buildType": "apk" } }
  },
  "submit": {
    "production": {
      "android": {
        "serviceAccountKeyPath": "./keys/play.json"
      }
    }
  }
}

Test yourself

Match each flow piece to its role

eas submit

Sends to store
Google Play

Android store
App Store

iOS store
service account

Android auth

Write the submit subcommand

eas ____ --platform android

Show answer

eas submit --platform android

Which key is used for iOS submission?
```
"submit": { "production": { "ios": { /* ? */ } } }
```
- googleServicesPath
- ascApiKeyPath
- serviceAccountKeyPath
- keystorePath
Show answer

ascApiKeyPath — ascApiKeyPath takes the path to the App Store Connect API key.

Next lesson: eas.json

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies