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

Error: Invalid value at 'track_config.releases[0].status' #127

Closed
valeriyo opened this issue Jun 30, 2022 · 4 comments
Closed

Error: Invalid value at 'track_config.releases[0].status' #127

valeriyo opened this issue Jun 30, 2022 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@valeriyo
Copy link

Why?

Creating a new Edit for this release
Validating track 'internal'
Uploading ./artifacts/com.example.app-release.aab
Successfully uploaded 1 artifacts
Adding 1 artifacts to release on 'internal' track
Error: Invalid value at 'track_config.releases[0].status' (type.googleapis.com/google.play.publishingapi.v3.Release.Status), ""
      - uses: r0adkll/upload-google-play@v1
        with:
          track: internal
          packageName: com.example.app
          releaseFiles: ./artifacts/com.example.app-release.aab
          serviceAccountJsonPlainText: ${{ secrets.SERVICE_ACCOUNT_JSON }}
@valeriyo valeriyo added the bug Something isn't working label Jun 30, 2022
@valeriyo
Copy link
Author

For the record, adding this line fixed it:

          status: completed

Hopefully this helps someone.

@skeeping
Copy link

skeeping commented Jul 5, 2022

thanks @valeriyo it helped me

ignyx added a commit to ClubInfoInsaT/application-amicale that referenced this issue Jul 16, 2022
@Del-S
Copy link

Del-S commented Jul 26, 2022

Seems like this is a duplicate of #85 which should be fixed by https://github.com/r0adkll/upload-google-play/pull/87/files. I checked the source and the change is in the latest version. But using uses: r0adkll/upload-google-play@v1 still produces this issue.

Adding status: completed helped. Thanks @valeriyo.

@boswelja
Copy link
Collaborator

Yep, please make sure you're pointed to the latest release (NOT v1). There are some pipeline issues that break updating the v1 tag

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants