My application is not submitted in Play store. Its a non market app, each time when we give an update, the application checks by its own and will download the latest build from our own server.
I have released application to my clients, for around 4 times. Each time i have
increased the version code from 1 to 4.
In my latest build i have not incremented the version code to be as 5, now i am getting a complaint from my client side that the new update is not able to be installed.
Whereas when i tried in my local device, its working good.
Does the version code affects the installation of updating a build
Yes exactly, version code effects the market build.
According to you, your code is checking on your server of a possible update via version of the app. As you have not incremented the version of the app this time, there is possible chance of error. Rest all depends upon your code. As far as google play is considered, you have to increment the version code each time you upload a new apk
Related
We have given two new updates in the last 15 days.
but still for some users its showing the older version of App.
We have increased the version code and version name with every update.
But for some devices still, it's showing the older version.
Here is the Scenario for the issue
The latest app is updated on 19 June
1.For the first time, the app store shows the Older version
version Code: 207
2.After that when user visit to play store again
and search for the same App it shows
the next updated version.
version Code: 209
3. Again After that when user visit to play store
and search for the same App it shows
the latest updated version which is on 19th of june
version Code: 212
We always upload the signed apk on Playstore.
Why it's not showing the latest update for the first time install.
Please help us with this
Thanks in advance
From Play Console support:
Due to device connectivity and varying server load, it
may take several days (in some cases a week) for app updates to reach
all devices. The behavior you are seeing with the update being
available on the web is common for apps. The mobile store will update
in due course.
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.
If this question I'm about to ask was already asked, please just direct me to the link as I didn't find it. For the beta testing in google play, do you have to first un-publish a beta APK before the new one will take its place? Also can you upload the same version code or do you have to create a new version code with each APK upload in Beta?
The reason I ask is I was about to Beta test a new version of an application. I upgraded the application on my test phone and it crashed. I found out there was a line of code I forgot to take out for testing purposes which caused the upgrade to break. Which is funny because the testing code was testing, indirectly, the upgrade code. Anyway, so I didn't want to upload a whole new code version just overwrite the pre-existing APK upload. I was hoping this was possible due to it only being in Beta status. Also, I guess this means having to potentially wait another 24 hours for his new Beta APK upload to take effect. That was another thing I was hoping to bypass was uploading the same version in Beta would wipe out the pre-existing Beta version code so the changes would be immediately upgradable. Wishful thinking I'm assuming.
Thank You in advance.
No, you do not have to un-publish your application to upload a new Beta version. However, you must increment the version code in order to release a new Beta version. The version code must be incremented, so devices that installed your application can track whether an update is available, by comparing the installed version code to the Google Play version code.
Every time you release a new version or update your application info, it could take a few hours for these changes to propagate. In my experience, it only takes about 5 hours until people start receiving the update notification. If you are really bothered by the time it takes for new versions to be available, you could use a different app distribution service, for example HockeyApp, TestFlight, etc...
When your app is ready to production, you don´t have to unpublish, just "promote to production", you don´t have to change the versionCode.
If your Beta application has bugs, made the changes and you have to upload another .apk and yes, you have to change to the newer versionCode.
If your app was published, you can´t overwrite the pre-existing APK.
Say I have an application that users have installed from the Play Store, if one of my users reports a bug and I want to send them a patched version of the app to test, they can install it to their phone just fine. But if I then update the app on the Play Store, will the user get the update? My testing seems to indicate this is the case, but is there any gotchas?
The way my build process works is that each time I build, it gets a higher version code, so the patched version will have a higher version code that the one currently in the Play Store and then the version I upload to the Play Store after sending my user the patch will have a higher version code again.
I'm taking a decently wild guess here, but it should work, provided the following are met:
The version code of the apk on Google Play is higher than that of the hotfix
The user originally installed the app from Google Play to begin with, and only updated it via side loading.
The hotfix and the Google Play update are both signed with the same key.
I'm decently sure this will work, as I recall a long discussion about this on one of the android google groups that ended with success. I unfortunately cannot find it right now.
If you do try it out, please post back with the results.
I don't see any issue with this workflow. As long as you increment the version number at each build.
I published my first app in Google Play today, woot! Once I saw my app listed in Google Play, I realized I needed to make a change and post an update.
I made my code changes and incremented versionCode and versionName in the manifest file. I then built my apk, signed with the same key as the original apk submitted to Google Play.
I uploaded a new apk, deactivated the original apk, then activated the new one and clicked Save.
I waited a couple of hours, looked in Google Play and could see that yes, the new value I put in versionName had updated.
On my Android Phone, I had originally installed the first version, but when I go to Google Play on that phone, I see the new version of my app, but the only options are "Open" and "Uninstall".
What do I need to do to my app in the Dev Console, or wherever, so the Update option appears when me or any other user goes to my app in Google Play?
Doing some research in Android Developer, I read this:
android:versionCode
An internal version number. This number is used only to determine whether one version is more recent than another, with higher numbers indicating more recent versions. This is not the version number shown to users; that number is set by the versionName attribute.
The value must be set as an integer, such as "100". You can define it however you want, as long as each successive version has a higher number. For example, it could be a build number. Or you could translate a version number in "x.y" format to an integer by encoding the "x" and "y" separately in the lower and upper 16 bits. Or you could simply increase the number by one each time a new version is released.
http://developer.android.com/guide/topics/manifest/manifest-element.html
Then I found this:
Google Play can manage updates to preloaded applications, provided the following conditions are met:
Package Name with the same Version Code of pre-loaded app must to be uploaded to the Developer Console
http://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=113476&topic=2365760&ctx=topic
So I'm confused, do I increment the Version Code or not. I'm pretty sure I should increment it, but then again the Update option is not showing up.
Congratulations on your first app! It's a very exciting moment!
Yes, you increment your Version Code when you make an update to your app.
When you were testing your updated version, did you install the apk file onto your device? You might have updated it unknowingly. Google play will therefore detect that you have matching version codes with the app on your device and the app you uploaded and will not offer to update it.
You must always increment the version code when updating an app on Google Play. Your update will not be accepted unless you do.
As for your update not showing up, Google Play takes time to refresh it's servers. My updates have sometimes taken more than 24 hours to be pushed to the device, while new installers get the latest version withing 2 hours usually.