You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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 nametv: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
Reproducible demo or steps to reproduce from a blank project
eas.json
And running any build command, e.g
eas build:list --limit 1 -p android --json --non-interactive
The text was updated successfully, but these errors were encountered: