I am having problem pushing my build to Google's Play Store.
I suspect the recent lowering the minimum version from 23 to 22. I have published quite a number of beta releases (no prod release yet).
Is it possible to lower the minimum API version after we publish a beta release?
How do I invalidate all the beta releases?
Is it possible to lower the minimum API version after we publish a beta release?
You need to change the minimum API version in the AndroidManifest.xml and update the apk to Google Play Store.
You could refer to this article for how to update the apk.
Related
I'm facing an issue while uploading to the play store.
This issue
Your app currently targets API level 30 and must target at least API level 31 to ensure it is built on the latest APIs optimized for security and performance. Change your app's target API level to at least 31".
If Change the target SDK version some of the features are not working.
Is there any solution to upload to the play console without changing the version of the target SDK.
Let me give an example.
App version 1.0:
Minimum SDK is 17+
App version 1.1:
Minimum SDK 21+
So John with a device SDK 18 can't get the latest version (1.1).
But if he goes to play store with the app link, can he still download the previously supported version (1.0) or not?
If I have updated as usual on Play store, the old version won't be available to old SDK users right? I only want the latest version available. If older device view it, no longer supported is what we need.
Just want to know how Play store handles this situation. Thanks.
I need help for removing the beta app submitted in google play store, Recently I have submitted my app with Targeted SDK version 23 for beta testing but now I want to submit the app with targeted SDK version 15 for production.
I have tried by submitting the App to Production with targeted SDK version 15 but it showed me an error saying:
Permission model downgrade PROBLEM: Users that have the APK version
code XXXX1, which targets SDK 23 or higher, will receive an error when
they attempt to upgrade to this apk XXXX2 because it targets SDK 15.
Is there any way to delete the existing beta app or to submit the production app with SDK15 other than un-publishing the app? Un-publishing the app will cause the inconvenience to existing users.
There is no way to delete a build from the Alpha or Beta channels. What you have to do is, deploy an artifact with a higher build code to the channel, then promote the channel to production. The APK that you want to remove will not show up, only the build with the highest build code, so there is no risk to doing this.
(source - just worked with Google Play support on a similar issue.)
Currently, I have a production app, which is using SDK 21.
Since it requires a huge engineering work, to port the app to SDK 23, we make another unstable Alpha release, by using SDK 23
Today, I need to make a critical bug fix release, for our production app.
However, since we have an Alpha app with SDK 23, it prevents us from publishing the new production app, which is using SDK 21.
I try to de-activate Alpha testing, but it just won't help. Please see my screenshot.
Anything I do, so that I can publish my critical bug fixed production app, with SDK 21?
Thanks.
I get pretty useful advice from ianhanniballake
You upload a new prod build to prod (target API 21, higher version
than current alpha version number - what you're showing us) and a new
alpha build to alpha (target API 23, higher version than new prod
build), then publish both simultaneously.
That way alpha users get updated to a new API 23 build and prod users
get updated to a new API 21 build and importantly no API 23 using
alpha build is offered an API 21 build.
alpha > beta > prod always - remember it is set up so you can promote
alpha to prod eventually (which wouldn't work if prod's version number
was larger than alpha)
In short, switch to advance mode, upload 2 APKs which targets different SDK. Make sure alpha version code is higher than production version code.
A very lengthy explanation can be found in http://developer.android.com/google/play/publishing/multiple-apks.html
Also, don't forget to click on deactivate button, of current alpha and current production before publishing.
My app is intended to only run on API level 20+.
Unfortunately my fist APK that I published was targeted towards API level 11+.
I fixed the issue and uploaded an updated version. Now I have two APKs that are active and published. If trying to deactivate one of them I am getting an error that downgrading is not allowed.
How do I solve this?
You should deactivate the oldest version so if version 1 is API 11+ and version 2 is API 20+ you should deactivate version 1. This should disable downloads for devices that are < API 20. If a lot of users have it installed you can't force them to update so you will have 2 version running until your whole userbase has update to that version.
Found the solution:
I had to deactivate an older APK from the beta-phase. After that I was able to deactivate the +11 APK.