Reputation: 519
Usually the when the application gets released in the Internal Channel, the build will get reflected instantly. Within a minute.
But strangely the build is not reflected even after a day. I am using the latest new Google console which displays the status as, ('Release not live' and not 'Being Reviewed')
Can you help to understand the behavior or the cases which might cause this
Upvotes: 22
Views: 12396
Reputation: 2386
In my case, I didn't have testing at all and released straight through Production
menu.
I had versionName "1.00"
with versionCode 1
. Since it's the first submission, it would take few days before it gets approved and while awaiting for approval, I added a functionality in my app.
I uploaded a new build with versionName "1.00"
with versionCode 2
.
I turned off Managed Publishing
and waited for approval. Few days passed and both builds went Superseded
or Release not live
.
TLDR; I turned Managed Publishing
to on again and my second build was successfully published!
Upvotes: 0
Reputation: 503
This can also be because you have previously paused the track.
The track needs to be resumed.
Hope this helps someone as I have stumbled upon this myself and spent some time until I noticed the track was paused (I forgot about it)
Upvotes: 2
Reputation: 8573
I had another problem, so I summarize the both fixes.
Under Testing>Open testing>Testers
fill the following
Your bundle/apkversion code may be greater than the Internal Track's bundle/apk version code.
If it's your case, you'll have to publish a newer version.
If the publishing overview is set to Managed publishing on
it wont be released neither.
Publishing overview
managed publishing
to off
(top right)>Setup>Advanced Settings
Unpublished
Cheers
Upvotes: 3
Reputation: 11
I experienced the same thing. For me I had to complete the "Feedback URL or email address" field as stated above. Also in addition to that I had to go to App content and complete the Privacy Policy step. When I had declared that my app complied with Google Play Policies the status changed from "Release not live" to "Available to unlimited testers". Hope this helps someone.
Upvotes: 1
Reputation: 1216
This was happening to me when published an open beta version, it was the first release so in my case it was not a superseded version problem. I fixed it by completing the "Feedback URL or email address" field in the Open testing > Testers (Tab).
After doing that the status changed from "Release not live" to "Available to unlimited testers" with the green icon.
I've found it by pure luck since Play Console does not indicate where is the problem.
Upvotes: 26
Reputation: 1337
This usually happens when you have a production bundle/apk with a version code greater than the Internal Track's bundle/apk version code. Check if that's the case.
Upvotes: 5