Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
sebryu opened this issue Jan 21, 2025 · 1 comment
Open

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

sebryu opened this issue Jan 21, 2025 · 1 comment

Comments

@sebryu
Copy link

sebryu commented Jan 21, 2025

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

@sebryu sebryu added the needs review Issue is ready to be reviewed by a maintainer label Jan 21, 2025
@szdziedzic szdziedzic added issue accepted eas build and removed needs review Issue is ready to be reviewed by a maintainer labels Feb 3, 2025
@expo-bot
Copy link
Contributor

expo-bot commented Feb 3, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants