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.
Related
I couldn't find any similar topic in here or google. I uploaded an app in play store and then I uploaded a new version of it. But now, It always asks for an update in market. I don't know is it due to my code or something. When I upload an update I increase the versionCode and rename the versionName in android studio then sign it
Then I go to play console - select the app - release management - release dashboard
Then I release my new version. I select "Android App Bundles and APKs to deactivate". I don't click "retain" It seems like a stupid post but I don't know what the problem is. I did it before I've never faced such an issue. I do everything like described in here https://customersupport.doubledutch.me/hc/en-us/articles/360001395033-Android-How-to-Update-an-App-in-the-Google-Play-Developer-Console
Finally it always asks for update in the market
I would be glad for any tiny idea. If stackoverflow is not the correct place for this post can you at least redirect me the correct place? Thanks.
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.
I've recently released an Alpha build of my app via Google Play Console (as I've done many times in the past). This is a closed testing build and I've opted in with my device/account via the URL console provides.
There is an existing production version of the app.
I waited a little while then went to PlayStore app to download the update.
Strange thing is, the version shown in PlayStore is updated (to the one used by my Alpha build) but there is no option to 'Update', only the option to Open the already installed (older) production version I have installed on my phone.
Has anyone seen this before? Could it just be Google are still in the process of rolling out my Alpha build?
Update
I've waited over 12 hours now since upload to console
I've tried clearing the cache on the PlayStore app to see if the update option appears but it didn't.
Update 2
I've got the update to work but in a very convoluted way. I had to:
Open the 'download' link on the testing opt-in page using Chrome (not PlayStore)
Click 'Buy' (not Update) and let it install
The result is though that it didn't seem to update the app, rather overwrite it. As a result a migration routine I had in the new app to pull over old data didn't run and my previous app data was lost (this is a separate issue though).
It does sound like something is wrong with my PlayStore app but what!?
This is weird. This sounds like you changed package name (essentially released a new app) rather than just release a new Alpha.
I have recently updated my Android app from Google Developer Console. I have updated my app from 1.1 version to 1.2 version. But how i would know that an update notification has gone to all active install user of my app.
Whether i need to write some code or is there any option available in Google Developer Console...
Please help me out , i need this essentially.
At the moment, the only way to tell is by day to day statistics from the google console to know how many have updated to your new version.
Go to statistics windows, then underneath the first graph there should be an option to display Active Installs by App Version.
Even if all your users update the app, there may be backup copies. Normally, such copies are never used, but on really rare occasions something happens and... it will be really very frustrating if the backup copies get broken in the course of time.
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.