One of my existing launched app's minSdkVersion is 4, but now I want to provide an update , which minSdkVersion is changed to 5.
I have tried and upload to the market is okay, but what will happend when this update is really being rolled out?
What would happen to the user with device can't meet the requirement? Any side effect except they won't be able to install the app in the future?
Thanks.
If you "deactivate" old apk file in developer console - your app will we able for downloading only for API 5+. There will not be any effect for people with API 4 and already installed app.
If you keep both old and new apks in market in "active" state, then market will offer old one for people with API 4 and new one for people with API 5+. Also they will be offered to update your app.
When you add apk that supports less versions than old one, you will see this:
http://take.ms/E0SYg
Market resolve itself what apk to give user.
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.
As the title says, we published a new version of an app 2 weeks ago. Play Store indicates in the registry that the new version was uploaded (1.7), and allows it to be downloaded to users who did not have it. Not so, for those who already have it, for example, users who have version 1.6, do not see the option to update, just uninstall or open.
We expected it to be only a matter of time, but 2 weeks is already too much. We contacted Google support, and they only ask us questions like: "Have automatic updates for the application enabled?" ... Does anyone know what is happening, or if it is our mistake, some step wrongly made? We generate the apk directly from Android Studio and change the version.
One of the issues that your users might have is this
Maybe they disabled the auto-updates of Google Play, but is really weird that they can't see it, maybe it's due the devices. Is your device listed as compatible with the new version of your app? Did you tried clearing Google Play cache and trying it again?
PS: Make sure you change in your Gradle (Module app) your versionCode along with the VersionName
If new users are getting the new version installed then it is definitely uploaded to the Play store correctly.
If existing users aren't seeing "update" (just open) then it means there is something about the new version of the app that is incompatible with their devices. You can check this by trying uninstalling and re-installing. If they get the old version after an uninstall / re-install (or worse, if they can't install after uninstalling) it shows that only the old version is compatible with their device.
This probably means you changed something in the manifest to make it incompatible, but that is a whole different debugging problem.
When my personal phone upgraded to Marshmallow (6.0.1), my app became no longer visible in Google Play.
The manifest has:
Minimum SDK: 10
Target SDK: 22
No maximum SDK
I tried uploading a test app with everything the same except with Target SDK = 24, and it did show up in Google Play.
While I could upgrade the app for Marshmallow, I would rather not have to.
What is going on and can I do anything about it?
Im might be wrong, however, I believe you have to update your manifest and upload the apk again.
Basically, your current manifest is targeting devices with android version from 10 to 22.
You have to change your manifest and set target SDK to 23.
This is expected since your app may not work well in android MM.
You are responsible to update the manifest, test and only after that, upload the new version to Google Play store.
Now I feel really dumb, and not to happy with the Play Store search algorithm!
The app is still visible. But, even though I searched for it by the starting two words of its name, it was so far down in the play listings that I didn't see it. This is an app with over 10,000 installs and a rating around 4.5 and current sales.
So, if you don't see you app in the play store on a device, scroll all the way through the category, or put in the entire name.
I'm currently involved in an open source project which I regulary release in the Google PlayStore. As the statistics of android-usages show that less than 10% of my users use android 3 or lower I started to wonder if I should switch to Android 4.X. This gives me some more functionality which I can't include at the moment (SettingsFragment for example, which isn't even inside of the support library).
When I release a newer version with higher requirements in the PlayStore - what will happen to my users which don't fulfill this requirements? What about users who want to install my app with low android-versions? Is my app hidden for them as soon as I upgrade the app? Is there any chance that my current version of my app can still be found by lower devices and the newer version is available for newer devices? I would like to avoid having two seperate apps in the playstore as I would lose a few people.
I couldn't find anything in the Google-Docs so I needed to ask for help in this glory community ;)
You can target multiple different APIs using multiple APK's. Just use your current version for old versions and create a new APK for everyone else. More here: http://developer.android.com/google/play/publishing/multiple-apks.html
Hope this helps, let me know if you need more info.
I have an app on the marketplace, minSdkVersion is set to "3". I want to change it to "4" in my next release. Will existing android 1.5 users be affected by this, if they already have my app installed? I'm hoping they can continue using the app as is, they just wouldn't see it appear in the marketplace anymore?
Android 1.5 users who have already installed the app won't be affected, but they won't be able to update the app and use newer versions. That's because the minSdkVersion is now 4, and they use Android 1.5. They will neither see any updates nor be able to install it (if they uninstall the current version).
They will continue to be able to use the application that is installed on their phone. However, if they remove it, they won't be able to download it again. It shouldn't remove it from their phone if they do an update, if that is what you are worried about. It just won't see the update.