Google Play Publisher API edits.Tracks Status Resource missing IN_REVIEW status [179708468]

Bug

Status Update

No update yet.

Description

da...@lyft.com

created issue #1

Feb 9, 2021 07:07PM

Detailed Explanation

The Android Publisher API does not accurately reflect the status of a release as IN_REVIEW when the app is being reviewed internally by Google before being allowed to be published to the Play Store. Currently, the response incorrectly returns "IN_PROGRESS" for releases that are in-review.

Steps to Reproduce

Log in to the Google Play Developer Console with an account that has a published app in the Google Play Store
Submit a new release to be published
Locally, authenticate with the Google Play Publisher API
Perform an API call to request a new editId
Perform an API call to list all tracks for a given package_name + editId

Expected: the release you published will show as IN_REVIEW

Actual: the release you published returns a status of IN_PROGRESS

Possible Fix

Ideally, there'd be a new status that would accurately reflect the state of the release.
The Status documentation would also be updated to include a reference to the new status: https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Status

Notes

For context, developers use the Android Publisher API to keep track of and manage releases on the Play Store.
https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks#Release

Comments

is...@runway.team <is...@runway.team> #2Jul 22, 2021 02:19PM

Really looking forward to a fix for this. The current behavior is really misleading because the status makes it seem like the rollout has started when it in fact has not. I think the recommended fix of adding an IN_REVIEW status makes a lot of sense.

ga...@gmail.com <ga...@gmail.com> #3Jul 22, 2021 02:37PM

➕➕ this is extremely important to our team

ma...@gmail.com <ma...@gmail.com> #4Jul 23, 2021 02:44PM

Definitely affecting us and also I agree 100% with the proposed solution.

jo...@gmail.com <jo...@gmail.com> #5Sep 5, 2022 08:24PM

Has anyone found a workaround for this yet?

jo...@gmail.com <jo...@gmail.com> #6Sep 5, 2022 08:25PM

Even my rejected apks show as status completed.

dy...@iconsoftheia.com <dy...@iconsoftheia.com> #7Nov 3, 2022 10:49PM

+1 to this. Does anyone know any workarounds for this since post last year? Seems like Google has not fixed yet.

[Deleted User] <[Deleted User]> #8Feb 23, 2023 08:00AM

Comment has been deleted.

Message last modified on Feb 23, 2023 08:20AM

ak...@tramline.app <ak...@tramline.app> #9Jul 15, 2023 08:10AM

+1 to this. It is quite important for us at Tramline. Agree with the proposed solution.

bu...@gmail.com <bu...@gmail.com> #10Oct 3, 2023 03:28AM

Currently, the status on the in-review store is version 1.0.5, but when I get it it only shows the status of the old version that has been rolled out on the store.

image (4).png

1.1 MB

View

Download

kn...@squareup.com <kn...@squareup.com> #11Oct 20, 2023 04:32PM

+1 to this. It looks like an easy update, weird that it has not been fixed in two years.
I want to use publisher API here at Block, and the information the API provides for tracks right now is very scarce and unreliable

An...@walmart.com <An...@walmart.com> #12Oct 26, 2023 07:44PM

+1 here

is...@runway.team <is...@runway.team> #13Oct 26, 2023 08:36PM

While this issue is getting a bit of activity, I'd like to take the opportunity to flag a related issue:

https://issuetracker.google.com/issues/208842993

TLDR; Tracks Status is also missing any sort of indication of managed publishing state, which could also be easily remedied with an additional status. So two additional statuses would do the trick:

IN_REVIEW: when an update is either waiting for review or in review with Google
READY_TO_PUBLISH: if managed publishing is enabled, this status is returned if the update has not yet been published

ro...@gmail.com <ro...@gmail.com> #14Nov 2, 2023 06:05AM

+1!
This is extremely important to our team as well.

And I fully agree with the comment above from the Runway team, we'd need 2 statuses.

re...@skeelo.com <re...@skeelo.com> #15Nov 14, 2023 11:52AM

+1!
Please fix this asap

ap...@gmail.com <ap...@gmail.com> #16Nov 16, 2023 02:41PM

+1 this is very important to fix

j....@gmail.com <j....@gmail.com> #17Nov 22, 2023 12:05PM

Hi Google team,

Internally in our company, we're using the Android Publisher API to emulate a phased release. Every morning, a cron job checks if there is a release "inProgress," and if yes, we increment the percentage until it's available to all users. Everything was working perfectly until last month when we enabled the "Publish Overview" functionality.

Publish Overview allows us to send a version to review without making it available to our users. When approved, we can then go to Google Play and release the review. When a version is under Publish Overview, the Android Publisher API indicates that the app is currently "inProgress" with the pre-defined percentage set when creating the release. We believe the status is incorrect and should be something else until we send the version to the users.

[Deleted User] <[Deleted User]> #18Jan 9, 2024 05:48PM

We have a similar issue. Apps that are rejected have their Release.status returned as `completed` which is very misleading.
It seems we have no way to know if the release is In Review or Rejected using the API.

How can we get the attention of the Publisher API team to address this issue?

sa...@google.com <sa...@google.com> #19Jan 17, 2024 02:05PM

Hello,

The Publishing API represents your intention rather than what's already been approved or published. IN_PROGRESS represents a staged release, and COMPLETED - a fully rolled-out release. This is not to say that the release was approved, or indeed published. See more about these parameters in the API documentation [1].

We realise that, with the ever-evolving publishing features (Changes ready to send for review, Managed Publishing... [2]) this has become somewhat confusing. We do have plans to extend the Publishing API to include review/publish status, but unfortunately have no specific timeline for launching this.

Hope this helps.

[1] https://developers.google.com/android-publisher/tracks

[2] https://support.google.com/googleplay/android-developer/answer/9859654?hl=en-GB

sh...@adidas.com <sh...@adidas.com> #20Aug 29, 2024 03:31PM

Is there any update on the most wanted enum in Google Play ?!

er...@getjobber.com <er...@getjobber.com> #21Nov 14, 2024 09:57PM

The additional status would be game changing for app releases.