Im trying to rollout a new beta release of an android app.
I have uploaded the apk file to the Google Play console.
But in the release page I get the following warning:
While it says it is just a warning, I am unable to proceed with the rollout.
And as there are no other errors or warnings, I'm assuming the reason I cannot continue is due to this warning.
This app is only installed on 2 devices - the developers devices. The warning has no real consequences, as the app is in beta.
Is there anyone way to get passed this warning?
Same things happened to me with the version code 2. so I built and uploaded new apk with version code 3. Don't know how but it did work!
The rollout could be blocked because other parts of the app info you need to fill in are not complete.
On the left panel, make sure all the check marks are green.
This shouldn't block your rollout. If it is blocking your rollout, or something else is and the Play console isn't telling you what it is, then it is a bug in the Play Console. Please contact the Play Console support (using the Contact section under the help "?" icon) and they can check your exact details and work out what is going wrong. They can provide support using email and live chat.
It happened to me when migrated to androidx.
The numbers of affected devices for the new version was insignificant. (1 device out of 7000+)
I decided to continue with the rollout in spite of this warning.
Related
Our app update has been rejected even though we addressed the issue. In the email with the details of the rejection says that we have some vulnerabilities with our recent submission but it says that the version that have issue is the one on the production channel:
and we didn't submit that version because it's already public, my latest version is 2021031602 (3.3.0) and as you can see in the image above that version doesn't have any vulnerability and I want to upload it to a closed test channel not production. I post this question here because I'm unable to get a proper response from the Google Play Team.
This is the most recent chat that I had with them:
Then I get this email:
But I never got an answer from the policy team, we have been running with this issue since January and honestly I don't know what else can we do.
Anyone who has been in this same situation? I'll really appreciate your input.
Greetings!
I managed to solve the issue with the following steps, in case someone is struggling to find how to remove a non complaining bundle/apk.
Go to your Play Console.
Select the app.
Go to App bundle explorer.
Select the non-compliant APK/app bundle's App version at the top right dropdown menu, and make a note of which releases they are under.
Go to the track with the policy issue. It will be one of these 4 pages: Internal / Closed / Open testing or Production. (If the bundle with the issue is on the production track, you'll need to upload an update directly to that track until you get to the step 8).
Near the top right of the page, click Create new release. (You may need to click Manage track first)
If the release with the violating APK is in a draft state, discard the release.
Add the policy compliant version of app bundles or APKs.
Make sure the non-compliant version of app bundles or APKs is under the Not included section of this release. For further guidance, please see the "Not included (app bundles and APKs)" section in this Play Console Help article.
To save any changes you make to your release, select Save.
When you've finished preparing your release, select Review release.
If the non-compliant APK is released to multiple tracks, repeat steps 5-9 in each track.
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
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.
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.
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.
I had another problem, so I summarize the both fixes.
1. Missing feedback url
Under Testing>Open testing>Testers fill the following
2. Bundle/apk version
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.
3. Stuck on Publishing overview
If the publishing overview is set to Managed publishing on it wont be released neither.
Go under Publishing overview
Publish the content
If you do not have any version live now & this was the reason why you were using the Managed publishing
Change managed publishing to off (top right)
Go under >Setup>Advanced Settings
Select Unpublished
Warning: You can download an open testing version only if the app is published
Cheers
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)
I'm trying to push an update in the Play Store and I came across the following error. I'm aware of the new target API requirement which will be in effect from November 1st, but as of now, I'm supposed to be able to push an update to play store right? If that's the case, I'm not sure why am I getting this error.
Could some one please help me?
Thank you
That's a warning, not an error. It even says "Warning" right there.
You should be able to publish it anyway. The August deadline only applies to new apps.
This warning does not (or should not) have the capacity to block your release. There are two possibilities:
your release is being blocked by some other error as well which you aren't noticing because of this warning
there is a bug in the Play Console
If it is the second option you should report it to the Play Console support team. You can contact them via the help menu in the Play Console, which is behind the "?" (Question Mark) icon. But the first option is more likely.
I contacted Google Play Store support and they told me the issue is caused because of the version code number of the app. Though I updated the version, I forgot to update the version code number.
I fixed the version code number and uploaded the APK to the play store and it worked.
Thank you
Just upgraded an app from V12 to V13 - text change in help only. Works fine.
Go up upload it to dev. console and it will not publish the new APK, says:
"This configuration cannot be published for the following reason(s):
Version 12 is not served to any device configuration: all devices that might receive version 12 would receive version 13."
What is it talking about? V12 was published for 40K+ devices, I've just done exactly the same thing to three other apps with no problem, but this one won't have it.
No idea what it means. All I can do is save it as draft.
I think it is known problem of Google developer console.
Please see this answer
When you upload a new version of an app, you need to manually deactivate the previous version, until you do, the dev console won't let you publish the new state.
Both answers above equally good. I had tried the second one and it didn't work. Went back a few hours later, still didn't work, did the second answer again, and it did. Very strange ....
Another way to ask the question: how to make inapp billing working with all versions of my app?
I have got an app with inapp billing. I want to update it.
My active apk on the developer console is in version 1. My problem is the following:
when I install my updated app (signed package) in version 2 on my device using adb, I get the following message: "This version of the application package is not configured for Market billing"
when I install my updated app (always signed package) in version 1 (same version as the one on the console) on my device (what I can't do on the console...I have to increase the version number !) using adb, verything works...
Consequently, it seems that inapp billing works only with one version of the app: the one which is active in the console. I imagine that my users will have the same issue: only the users with the last update of the app will be able to perform inapp billing...the others will get the error.
Anybody knows how to solve this issue ? How can I do so that all my apps already installed in the world will be able to do inapp billing whatever the version number is ??
Thanks !!!
By "console" do you mean your publisher's account?
I think this isn't a bug but a feature by design. If you attempt to make a purchase that doesn't have one of the 4 android.test.* item ids, and it is running a debug version or even a release version that is newer than the one you have published, you will receive this error:
For example, if you're running on your device a Release mode that's one version higher than what's in the Market and you try to purchase a real item (not an android.test.* one), you will get the aforementioned error.
To further clarify: If you run an application of a higher versionCode than the one in the AndroidMarket (with the same package name, of course) it will succeed in "making the purchase" if you use one of the 4 android.test.* item ids.
Please note that this is based on my own experience and observation as full documentation on this leaves something to be desired.
Here is what I have observed while using In-App-Billing.
When you upload your release apk (regardless of Alpha/Beta/Production), IAB will not work right away, you will have to wait for a few hours before it can work
Uploading a new version of the apk (higher version) will also be the same. You will have to wait for a few hours for it to eventually work. The older version with IAB will still work though. What I usually do is to upload my release apk as Beta, wait a few hours, then when it is already working, promote the apk to production.
i face this error. solution:please upload sign apk and test with your Product id:com.test.purchased and set as a in-app product.
(1)run on your mobile using export with sign apk .
(2)if error is occur then wait 1-2 hours because sometime google take response late.