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.
Related
When I updated my app to use target API 30 and above, in android 12 the app was not detecting whether google fit is installed, I decided to use QUERY_ALL_PACKAGES permission and I was able to discover installed google fit. But when I submitted the app to the play store, it got rejected and I was told to use a Less broad app-visibility method
I don't know how to do this, I have tried adding the queries element to the manifest file and then passing intent filters for google fix, but it did not work because of errors caused by root packages.
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.
I have an app which I have been developing for about a year and I just pushed out a new version onto the google play store. I see the new version just fine on my own phone but my girlfriend's phone still sees the previous version.
I switched from eclipse to Android Studio for this release and thus was using Gradle for the first time. But I made fairly sure that the permissions, etc remained the same. One major change that was done was that in the previous version it was only supported up till api 16 but the new version allowed api 15.
I don't get why my girlfriend's phone can't see the new update.
If someone can advise, it would be deeply appreciated.
Thanks
Edit:
Something stranger about the whole thing is this. On the store listing, I changed the icon, feature graphic and promo graphic as well. The old one still appears on her phone.
More than one week ago I deployed version 1.0 of my apk on Google Play - no problems. On January 6th, I deployed version 1.1. After Google Play had updated the apk for public, I got the update trigger both on my Android tab and on my smartphone. Unfortunately there was a bug in the last version, so I updated again to version 1.1.1 on Janurary 7th and deployed it on Google Play. It's already provided to public. This usually takes about 1 - 2 hours. If one downloads the app, he gets version 1.1.1. I already tested that. But since the latest update, both my smartphone and my tab doesn't get the update trigger anymore. So they don't know that there is an update again. The deployment was 12 hours ago, so there must be the trigger by now. With the update on version 1.1, I didn't have problems and I got the trigger as soon as Google Play updated the apk for public.
Any ideas why the update trigger doesn't work and both Android 3.1 tablet and on Android 2.1 smartphone? I guess it's a Google Play or apk issue since it doesn't work on both devices.
(The version name and number in AndroidManifest have been incremented. Otherwise I wouldn't be able to update the apk on Google Play)
What I noticed: Google Play haven't updated the statistics for my app since Jan. 6th although it should update daily (and it worked until 2 days ago). Maybe it's based on the same issue.
I think I know what's going on, but I can't definitely say if this is really so. Google changed something in Google Play (like recently the concept of some implementation issues like Google Play Services instead of MapView), so I think that Android versions beyond Android 2.2 and above are already too old for the last changes (They cannot even use Google Play Services). Maybe that's the reason why it doesn't work. On my Android 3.1 tablet it obviously works again. At this one time as it didn't work, there was maybe a bug in Google Play.
It this is wrong, plz correct me.
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.