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.
Related
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.
im very new to the google play and mobile app world.
I would like to know the process of updating my app on the google play store as im not sure how. It is Android app.
I am using xamarin for the app. I have increased the version name to by .1 and if I do this, do I have to also increase the version number to 2 ? because it cannot take decimal points.
I have a simple understanding of It so im not sure if I have to create a new apk or update the existing one, and if so, how ?
and then on google play, do I just go and select the new apk, or updated apk ?
Thanks in advance
The version number (or version code) it's an integer value used to determine whether one version is more recent than another. This is not shown to the end users. Every new version you make should have a higher number than the previous. You can simply increase the number by one each time a new version is released.
The version name is a string, and it's only meant to be shown to users. It can be whatever you want, like "1.0" or "Beta 1.2.3".
To update an app you just upload a new apk to Google Play, and the system uses its version number to find out what's the newest apk ank make it visible by default.
There is a very good, detailed, step-by-step process at http://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/publishing_an_application/ (which also explains the difference between version # and version name, among other things). Definitely worth a read!
I am not exactly sure when I need to be changing the versionCode/versionName values in the manifest file before creating a new .apk and putting it on my own device.
Is it ok not to change them at all if I am just going to be testing on my own phone?
Thanks!
No, you can keep it the same if you are just testing on your phone.
Actually, the version codes and the version names come in handy when you are actually publishing your application on the market, enabling the users to know which version they have and what is presently available on the market.
But, since for the time being, you are just testing on your own, you can keep that the same. Won't be the cause of any problems.
Short answer: No, you don't need to change them
More Detail: For testing on your own phone, you'll be fine not changing them. It won't crash anything. Depending on your use of the Emulator you may be testing on your device quite frequently, and that would be a major pain! For me I never change them during testing, and I use my phone for testing pretty much exclusively (I can't stand the emulators).
It would however be wise to change them when you publish apps to the Google Play store in order to accurately represent the updated versions to your customers. They appreciate details like that.
Most of the times you would like to increment the version to keep track of bugs and on which version the bug was fixed. So mostly for tracking.
Other than that, the version number won't affect.
The only time when you may have trouble is when running a developer build(Installed directly from Eclipse) and running a standalone apk. Only in this case you may require to uninstall the previous app, but even then, the version number won't affect, since it is related to the signature and not the version number.
There is not need to change it if you are testing.
If you are putting it in the market and updating it,
Version Code is an integer that should be incremented,
Version Name is the name that will be show on descriptions.
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.