eas submit --latest does not submit latest build

In your post, please share:

  • bare workflow
  • eas-cli version: 0.49.0

1: run 'eas build -p android --profile preview --clear-cache --non-interactive --no-wait'
2: eas,json build preview config looks like this

"preview": {
      "extends": "base",
      "distribution": "internal",
      "releaseChannel": "staging",
      "android": {
        "gradleCommand": ":app:bundleBetaRelease"
      "ios": {
        "scheme": "scheme BETA"

2.5: eas.json submit looks like this:

"preview": {
      "android": {
        "serviceAccountKeyPath": "./fitbodyapp-google-api.json",
        "track": "internal"
      "ios": {
        "sku": "com.x.y",
        "bundleIdentifier": "com.x.y",
        "ascAppId": "x",
        "appleTeamId": "x",
        "ascApiKeyPath": "./AuthKey.p8",
        "ascApiKeyIssuerId": "x",
        "ascApiKeyId": "x"

3: Build runs fine
4: run 'eas submit -p android --latest --non-interactive --profile preview --no-wait'
5: Submit fails saying I have already submitted a build with this version number.
6: run 'eas build:list'
7: Latest android build is

ID               8bd9f282-26ce-46be-9aee-48137a2a232f
Platform         Android
Status           finished
Distribution     internal
Release Channel  staging
SDK Version      44.0.0
Version          4.5.3
Version code     3147303
Commit           ca32b6adc7bcb714b1c14c0ec7512a9be42c345a
Logs             https://expo.dev/accounts/fitbodydev/projects/fitbody/builds/8bd9f282-26ce-46be-9aee-48137a2a232f
Artifact         https://expo.dev/artifacts/eas/igCpjjJcmvnbzjCGMAb4Za.aab
Started at       4/12/2022, 12:23:50 PM
Finished at      4/12/2022, 12:43:36 PM
Started by       fitbodydev

8: Look at eas submissions portal and the lastest failed build is for the complete wrong channel, version number, build number, etc
Screen Shot 2022-04-12 at 1.02.52 PM
9: eas submit is not submitting the latest build. This is happening with both ios and android and all works correctly when I use the production scheme which is almost the exact same with the exception of using beta flavors/schemes instead of production flavors/schemes.
10: Is it not possible to push builds with “distribution:internal” to their respective stores?

This ended up being causes by the internal distribution setting on the build.

1 Like

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.