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.
Related
Deploying a Kivy app to Google Play Store is a true pain. I spent over a week now trying to deploying the app to the Play Store, whereas I spent only 5 days developing it.
After managing to overcome all problems during the build process with buildozer, I'm facing now another problem when I want to deploy my app to google store. This is the warning I'm getting:
Unoptimised APK
Warning:
This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimising your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower installation success rates and take up storage on users' devices.
Resolution:
Use the Android App Bundle to automatically optimise for device configurations, or manage it yourself with multiple APKs.
I know It's just a warning, I can ignore it right? I thought so too, but google store is not allowing me to deploy my app. So I must somehow solve this issue so that I can finally deploy my app in peace.
Here are the steps I'm making to build my app:
I followed all these steps (signed the app with key etc...)
I even tried using jarsigner as an extra step since the steps above didn't work
I also tried using zipalign to "optimize" my app
But none of that worked. Still google store is saying I need to make a bundle android app. But I'm using kivy/python so I can't use android studio to make a bundle and I can't find in buildozer docs how I can do this or if it is supported.
My app size is 28 MB, I even tried to remove some necessary stuff just to see whether it will work. So I reduced the size to 14 MB but that didn't work either. It's really frustrating. Building apps is fun while coding but the deployment process is real headache.
Here is a link to my app in case you want to play with the code or see the buildozer.spec file. I lost hope of uploading it to Play Store, hence I open sourced it.
Edit
here is how the google play console looks in my case:
This is the first tab, where I upload the app:
This is the second tab, where I should review and then release (notice here that I can't press the roll out to production button):
As you guessed, the message you're seeing about using AAB is just a warning, it doesn't prevent you from releasing the app. You're far from the first person to be confused by it though, the google interface is quite unclear.
The actual problem is that you need to make sure all the essential information is filled in on every page of the app store configuration. In your screenshot above, pages that have been completed are marked by a green circle with a check mark. In contrast, the "Store Listing" page only has a greyed-out check mark, indicating that you need to add something there before you can release the APK.
As discussed in comments, it turned out that the missing thing was screenshots of the app, and after adding them it could be released successfully despite the warning message.
I have Checked all the Things like...
App content
App release
Store Listing
Content Rating
Pricing and Distribution
Not a single thing remain but still not getting button enabled..
(Previously i have successfully updated my app in APKS format)
wanted to update in app bundle format i don't thing this may be issue (modified and upgraded my app version etc).
Successfully Solved the issue...
What was the issue : The Error says You can't rollout this release because it doesn't allow any existing users to upgrade to the newly added APKs
How to solve : You also need to Upload APKS and maybe need to leave one of the Apk so you can ignore the another error like "one of the Apk is overriding the app bundle".
So in conclusion upload apk with app bundle and leave one of the Apk just select which one you want to leave...
Note :
Built using as split per abi....
And
Read error if you have any future error and try to solve it accordingly... :)
Had the same problem with flutter and google play console. I had mistakenly given earlier version as 4003 and had hard time with errors in google play console. Solution was just one line in
pubspec.yaml
The version is on the following line after the '+' sign and in my case it had to be bigger than 4003, so this one was fine:
version: 1.0.6+5000
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 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
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.