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
Related
Here is the scenario we are in:
We recently pushed an apk to the play store - the manifest file has the maxsdk version set as 26. This means that for the users with version 8.1 of Android does not see the app for download on the play store.
What we want to do is create another apk without the maxsdk version and upload to playstore replacing the existing one - no change in code as we have already tested the apk with version 8.1. However, we are concerned that the users who have already downloaded the app will get an "update" which is not really an update.
Can someone suggest the best way to deal with this?
You can achieve this by uploading an APK with minSdkVersion=27, and include the previous APK in the release, i.e. you'll have both APKs in the release but your existing users won't be eligible to release the new APK so won't see the update.
Then, in your next "real" release, you go back to your normal minSdkVersion and go back to a single APK per release.
It's a bit hacky but achieves what you want.
Hope that helps!
The best way would be to simply release a proper update, which in the version description simply says that you added support for Android 8.1. If you're updating the SDK, you are indeed making an update, and this sort of 'update' is commonplace.
Users won't be put off by the fact that there's an update that is exclusive to a particular Android version (which they may not have), as it will show that you're committed to supporting the latest firmware.
I have rolled out my apk to 5% on Google Play, now I suddenly found a critical bug which I fixed, is it possible to roll out another apk on top of older one without it increasing it any more further?
is it possible to roll out another apk on top of older one without it
increasing it any more further?
Yes its possible.
You need to increment the version number and version code of your app (in the AndroidManifest.xml) and build a new apk and upload the same to Play Store.
The users who haven't received the previous update will directly get the new update and the users who have already got the previous update will get a new update on top of it.
I am developing an Android application and in this application, I am using "In app billing" features.
I uploaded apk on the google console account and set the product id, price and other required things and saved all the data in the draft.(Application is still in draft mode).
I did not publish my app yet.
After a few minutes, I realized that I uploaded old signed apk file and keystore of this apk has already lost.
Now I want to remove this old apk file and want to upload a new one in draft mode.
My problems are :
How to remove the old apk file from the google console account.(In Draft Mode)
How to upload the new signed apk file with new key store (As I have
lost my old key store)
EDIT:
I want to publish the app with the same name and with same package name. I do not want to change my app name atleast.
This can now be done by going to Release management > Artifact library and deleting the APK.
You cannot delete the artifacts anymore.
Here's a part of my chat with Pete through the built-in help & support.
Pete:
Thanks for waiting. You can't remove an apk that you've already
served. Your next Production apk has to be version code 3 or higher.
Me:
So I can't just delete the artifact of that build?
Pete:
That's correct.
(P.S. He mentioned version code 3 because of my specific issue)
You can try KOTIOS's answer.
Delete the aab / apk file from the Google Play Console on the App Bundle Explorer under Release Tab
Then select the apk/aab file you want to delete from the List
Quoting Can we still remove never-published apps from Google Play?:
Well, the answer is that the strategy still works. If you've never
published the app, you can remove all traces of it from Google Play
and another publisher account can then upload an app with the same
package name. All you need to do is deactivate (if necessary) and then
delete all .apk files and the app will disappear from your developer
console.
If the app was ever published, this will not work. You can unpublish
an app, but you cannot delete any .apk files that were ever active
while the app was published. (This behavior is undocumented as far as
I can find.) This is unfortunate; it would be nice to be able to
completely remove all traces of an app that was never downloaded by
anyone. Even better would be a sandbox area that emulated all aspects
of Google Play, including buying your own app (and would support doing
it through the emulator).
I also discovered that the delays involved in propagating changes to
all Google Play servers seems worse than it did a year ago with
Android Market. In one case, when testing license responses I had to
wait two hours after uploading (but not publishing) an app before the
response came back as anything from "NOT_MARKET_MANAGED".
You can do this by upload new apk with upper version
and the old Apk will deactivated automaticly
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.