So I'm having trouble uploading a new APK to the play store with billing enabled.
Currently I have a published app that is paid and I want to change it to a subscription app such that the users get a yearly subscription and hence latest data to the app.
Now my issue is that the developer console will not let me upload a draft APK with the permissions for billing enabled. I log into the dev console, go to APK, change from simple to advanced mode, save my new APK as a draft and once uploaded I get the following error:
This configuration cannot be published for the following reason(s):
All devices that might receive version 1 would receive version 2.
Some devices are eligible to run multiple APKs. In such a scenario, the device will receive the APK with the higher version code.
I updated the Version code and the version number to be one higher than the current as well as different combinations of upping only one of the two values with still no success.
The app is being signed with the same keystore.
Thanks,
DMan
Figured out what this actually means now. Basically it was just telling me that I need to archive the current apk in order to actually publish the new apk. The new apk was successfully added as a draft. This message was just worded a little awkwardly and actually means that in order to publish version 2 version 1 must be archived NOT that there was anything wrong with the saved draft I performed.
Thanks,
Dman
Yes, all you have to do is to disable the old aplication, after that a the Publish botton will be available to push on the top left area so your new APK will be published
Did you disable your first version? By default, after uploading in advanced mode, both your first and 2nd version are activated. Looks to me like it's just saying that you've got 2 APKs active, that will reach the same devices thus one of the 2 is useless.
Related
I upload wrong version in android console, but i save the last one, it is the posibility to turn back into last version?
I lost the last package, i built a new one package but it is crashing in many old devices.
thanks!
Do you mean you published a wrong apk on you Google Play publish account?
Then there's no way to completely turn back to a previous version, but you can mitigate it. Just make a new publish but instead of drag&drop your apk select it from artifact library.
It should automatically change your wrongly uploaded apk to deactivated and your previous apk to retained Any user that could have download the wrong apk will still have it but at least no more users will download it.
After doing that you should upload a new apk with a new version number fixing the problem
I'm trying to add an application for beta testing for first time. I made a mistake and instead of adding it on beta tab I did it on production one.
I'm trying to cancel the publish process but I'm not able to do so.
I've switched to advanced mode and clicked "deactivate" but I get the following error
This configuration cannot be published for the following reason(s):
You must have at least one active APK.
I don't want to publish the App. This other question Unable to deactivate APK accidentally uploaded to Prod seems to indicate that there is no possibility to revert this mistake. How is that posible?????
EDIT
It seems I'll be able to unpublish this app. Is it possible to publish it again later using the same package id and just change the version?
No, you can unpublish but once your application has been live on the market you cannot delete it.Only older version can be deleted
You cannot cancel the publishing, at least I think that if you upload a beta apk with higher version name it replaces the active app.
The error I think it's because the app is not published yet it takes around 2 hours to publish.
My company has an app published in the google play store/android marketplace. One of the issues that we're fixing in the next version of the app is adding back xlargeScreen = true (it was somehow set to false in the previous version, so now the app isn't showing up on larger tablets). We're trying to get the alpha/beta testing setup so we can make sure we have all our problems fixed before we push the apk to live.
I've uploaded an apk to alpha and published it. I made a google+ community, added it to the accepted testers and sent out the link for the app. But, when we go out to the link and get set as testers nothing happens. If I go to the google play store, it shows the date for the newest upload to the account but the 'install' button attempts to install the previous live version (which is incompatible with the test device, yay!). Also someone else used their device and all the install did was install the old version to their device.
I've considered the "wait up to 24 hours for the publish to go through" being the problem, but the first alpha was uploaded Friday at lunch and would not work at lunch today, on Monday. I moved the old apk to beta and put a new one in alpha (more bug fixes yay) at lunch today. I checked all the settings and everything looks correct, but I can't see how I'm suppose to actually download the beta or the alpha at this point. And if I'm suppose to download the production version 1) How am I suppose to do that on the device that's incompatible with the production version and 2) how do I choose between the beta and the alpha version?
Ok, so it takes about 2 hours to be published for alpha/beta and it will be availible in the google play store in place of the live app if you opt in.
My specific problem was the the new alpha/beta apk was still incompatible with the device. I wish there was some notice on the page to show that you are viewing a test version (or better yet, a way to select alpha/beta/production on the google play page after you opt-in).
Turns out that <uses-permission> will in some cases make a device incompatible if it's missing the feature. Adding <uses-feature android:name="problem feature" android:required="false" /> for the offending permissions fixed my issue.
My application is currently in alpha. On the google play developer console, I accidentally uploaded a new APK as production rather than alpha.
In advanced mode, there is a deactivate button. But if I deactivate and try to save I get the generic message "The application could not be saved. Please check the form for errors." I don't see any errors on the form. How do I deactivate?
I tried uploading a later version to alpha - that seems to work - but I don't want ANY version in Prod, as my app is not yet ready for prime time.
According to a Google customer service rep I contacted:
The Deactivate button is provided in your advanced mode when you want to support multiple APKs but when your new update supports the same number of devices as your previous APKs, the system won't allow such update. So it is required for you to deactivate the older version in order to upload your new APK.
The Deactivate button is only useful for situations where you have multiple active APKs.
Furthermore, discussing with them, there is apparently no functionality at this time that allows for you to remove APKs from the Production tab once they've been uploaded to that tab, AND there's apparently no way to enable Beta testing if your app is unpublished, so at this point it seems there's no way to undo what you've done if you accidentally upload an APK to the Production tab by mistake. The workaround proposed by the representative was to change the package name of the app, change the keystore used to sign, and create an entirely new application.
Further discussion with the representative indicated that the "error" is that you can't have a Production tab without an APK if there was one there already, but it sounds like there's a bug in that it doesn't actually report that that's the cause.
In latest play console you can goto Publishing Overview->managed publishing status-> press manage button on right then turn on managed publishing
I am trying to upgrade the existing application by changing the following in the manifest file.
changing From
android:versionCode="1"
android:versionName="1.0"
To
android:versionCode="2"
android:versionName="1.1" .
I am using the same keystore, but when I attempt to publish the app using the Google Play Developer Console, I am getting an error saying:
"This configuration cannot be published for the following reason(s):
All devices that might receive version 1 would receive version 2.
Some devices are eligible to run multiple APKs. In such a scenario, the device will receive the APK with the higher version code."
How can I upgrade my app. Thank you very much in advance .
I did the mistake to switch to "advanced" mode and it saved the App as draft somehow.
Seems the developer console doesn't like that.
Delete the App, switch back to "Simple Mode" and upload the .apk again.
This worked for me.
The advanced mode is for uploading and managing multiple apks for the same application.
Simple mode is for uploading single apks so in most cases it should be suitable.
I ran in the same problem just tonight. All I had to do was to Archive the previous version and the draft message disappeared and a button to Publish the new version appeared.
Ya i got the same issue then, i did this and resolved the issue:-
Just deactivate the previous apk from the prod, and then upload new
apk and publish it. It worked for me hope will work for you too.
There's no need to delete the newly uploaded APK and switch to "Simple Mode" to publish an update if you're presented with above message. The wording may not be ideal, but it's telling you that you have two active APKs with different version codes, even though one is still in draft status, and that is something you don't want if you intend to serve different APKs to different devices. This is also indicated in the "Production" tab at the top, where it will display both the version code of the existing APK as well as the in-draft update.
Generally speaking, you should only be interested in multiple active APKs if you actually serve dedicated APKs to specific devices. Most apps just consist of a single, generic APK though. So assuming that is the case:
To activate your update (and thus publish the updated APK):
Click Deactivate next to the currently published APK.
Promote your update to Production (i.e. promote it to Beta first, and to Production from there).
Hit Publish APK at the top of the page.
Following these steps, you'll notice only a single version code remains in the "Production" tab and that the error message disappears. Once you've completed the last step, you'll be able to switch back to Simple Mode as you please.
Reloading the page helped hide this message.
I got this error when I had to use Advanced mode to activate single APK. I tried switching to simple mode to activate same APK but it didn't help.