new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Expo · EAS · all subjects

submit to stores

20 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Automatic app store submission with GitHub builds

Once a build completes from GitHub, you can automatically submit the app to app stores using EAS Submit. To enable this: navigate to the project's GitHub settings page, find the build trigger, click options, select 'Edit trigger', and check 'Submit to store after build'. Every triggered build will automatically submit to app stores configured in eas.json under the 'submit' field. Ensure eas.json is properly configured with correct app store credentials and submission profile.

EAS Build auto-submit feature

EAS Build supports auto-submitting successful builds to app stores via the --auto-submit flag and EAS Submit integration.

iOS EAS Submit requires appleId, ascAppId, and appleTeamId

For iOS app submissions, eas.json submit configuration requires: 'appleId' (Apple account email), 'ascAppId' (App Store Connect app ID number), and 'appleTeamId' (Apple Team ID).

EAS Submit configuration is separate from EAS Build in eas.json

EAS Submit has its own section in eas.json under the 'submit' key, separate from the 'build' key. It contains platform-specific submit configurations.

Android EAS Submit track property specifies release track

Android submit configuration uses the 'track' property to specify the release track, for example 'internal' for internal testing.

EAS Submit production profile example configuration

An EAS Submit production profile can specify Android track ('track': 'internal') and iOS submission details including 'appleId', 'ascAppId', and 'appleTeamId'.

Submit jobs use build_id from build output

The submit_android_build and submit_ios_build jobs receive build_id from the build job outputs: ${{ needs.build_android.outputs.build_id }} and ${{ needs.build_ios.outputs.build_id }} respectively.

Android track option in submit profile

The android.track field in a submit profile specifies which track to submit to for Android. Example value: "internal"

iOS ascAppId in submit profile

The ios.ascAppId field in a submit profile specifies the App Store Connect app ID required for iOS submission.

Can submit a build from several days ago

EAS Submit can be used with a build from several days ago; you do not need to rebuild. The eas submit command allows you to select from previously built apps.

Manual fallback with Xcode for App Store submission

If EAS Submit is temporarily unavailable, you can manually upload to the Apple App Store from a Mac with Xcode by archiving and uploading the iOS app to App Store Connect.

App Store Connect API Key for EAS Workflows

To automate submissions with EAS Workflows, configure an App Store Connect API Key using: eas credentials --platform ios. Select the production build profile, log in with your Apple Developer account, select 'App Store Connect: Manage your API Key', then select 'Set up your project to use an API Key for EAS Submit'.

Production build prerequisite for App Store submission

A production .ipa file must be created before submitting to the Apple App Store. Build it using eas build --platform ios --profile production, or build locally with eas build --platform ios --profile production --local, or use Xcode.

Basic eas submit command for iOS

Submit an iOS app to the Apple App Store using the command: eas submit --platform ios. On first run, it will prompt for your Apple ID and walk you through selecting a build to upload.

Build appears in TestFlight after submission

After submitting with eas submit, the build appears in TestFlight after processing, which typically takes 10-15 minutes. To release to production, log in to App Store Connect and submit the build for App Review.

How to find ascAppId

To find your ascAppId: Sign in to App Store Connect, select your team, navigate to Apps, click your app, ensure the App Store tab is active, select App Information under General in the left pane, and look for Apple ID under General Information.

Auto-submit with eas build

Pass --auto-submit to eas build to hand off the finished build to EAS Submit automatically: eas build --platform ios --auto-submit

EAS Submit works on macOS, Linux, and Windows

EAS Submit works on macOS, Linux, and Windows, so a Mac is not required to ship iOS builds to the App Store.

EAS Submit recommended over manual submission

EAS Submit is the recommended way to upload iOS apps to the Apple App Store. The eas submit command works the same way on your machine and inside CI/CD.

Releasing app to stores

To release your app on the app stores, you can use EAS Submit. For more information, see Submit to Google Play Store and Submit to Apple App Store. To create a production build locally, see the local production guide and then go through the app stores guide to submit your app.

Give your agent this brain