Unable to run eas submit for androidTV (invalid `track` field)

[sebryu]

Build/Submit details page URL

No response

Summary

Currently graphql schema for eas will take enum with 4 options as track parameter, but when developing app for AndroidTV (with expo/react-native-tvos) there is an additional prefix added to the track name tv:alpha as described in Google Play Developer docs.

We have even ended app with double prefix for one of our tracks, making tv:tv:alpha also a correct google play track for our use case.

While I understand that the eas-cli is designed to help developers avoid shooting themselves in the foot, I suggest allowing the track parameter to accept any string, with suggested values outlined in the description.

Managed or bare?

Bare

Environment

expo-doctor output not relevant for this issue

Error output

eas.json is not valid.
- "submit.production.android.track" must be one of [production, beta, alpha, internal]
    Error: build:list command failed

Reproducible demo or steps to reproduce from a blank project

eas.json

{
  "cli": {
    "version": ">= 14.2.0",
    "appVersionSource": "local"
  },
  "submit": {
    "production": {
      "android": {
        "track": "tv:tv:alpha"
      }
    }
  }
}

And running any build command, e.g eas build:list --limit 1 -p android --json --non-interactive

[expo-bot]

Thank you for filing this issue!
This comment acknowledges we believe this may be a bug and there’s enough information to investigate it.
However, we can’t promise any sort of timeline for resolution. We prioritize issues based on severity, breadth of impact, and alignment with our roadmap. If you’d like to help move it more quickly, you can continue to investigate it more deeply and/or you can open a pull request that fixes the cause.

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.

[kibs]

@szdziedzic any chance this could be reopened?

[algoORgoal]

@szdziedzic
This issue can't be reopened?

[algoORgoal]

#3031 (comment)
I created a pull request myself. Apparently this issue will be resolved with this pull request.

[algoORgoal]

@kibs @sebryu While expo team is working on this issue, I forkted the repo and deployed the fixed version of this on npm registry. Check it out: https://www.npmjs.com/package/@sleppy-navigators/eas-cli
eas build --local would work. However, eas submit cannot be bypassed since it eas backend validatese the track information. Therefore, I'm planning to use fastlane temporarily as below.

      - name: 👷 Build app
        run: |
          eas build --local \
            --non-interactive \
            --output=./output \
            --platform=${{ github.event.inputs.platform }} \
            --profile=${{ github.event.inputs.profile }}
        env:
          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}

      - name: 🏗️ Cache Fastlane gems
        uses: actions/cache@v4
        with:
          path: ~/.gem
          key: ${{ runner.os }}-gem-fastlane-${{ hashFiles('**/Gemfile.lock') }}
          restore-keys: |
            ${{ runner.os }}-gem-fastlane-

      - name: 🛠️ Install Fastlane
        run: gem install fastlane

      - name: 🚀 Upload to Google Play (Fastlane)
        if: ${{ github.event.inputs.platform == 'android' && github.event.inputs.should_submit }}
        run: |
          fastlane run supply \
            --aab ./output \
            --json_key credentials/android/service-account.json \
            --package_name com.sleppynavigators.studyup \
            --track track1