A few weeks ago, I've changed an App from internal testing to open testing on Google play. Lets call it build 20. Since then a few updates have been published and now the current version is build 27.
Yesterday I've noticed that if you download the app from Google Play, you'll get build 20 installed. The question now is: How can you ensure that Google Play delivers the most recent version when installing the app? Is there a way to force it?
A workaround to get the latest version is to visit the "My apps and games" section at the play store app, where the just freshly installed app shows up under available updates. Pushing the "update" button installs the app's latest version (build 27). However, it would be nice if the Play store would deliver the most recent version during initial installation. Do you have any ideas how to make this happen?
When you change from the Internal or Open testing stage to the Production stage, make sure that Staged roll-out is 100%
Of course, it takes several hours to distribute all new users or existing users
Related
Due to some reason, I do not wish to publish the already reviewed, App on Play Store. (Let's call this the buggy version - v1.0.3(5))
I have a new version uploaded with bugs fixed and version updated - v1.0.4(6)
I have Managed Publishing turned on.
What will be the behaviour after I click on publish changes. (When both versions are ready to publish).
Note: I do not want any user to use the buggy version - v1.0.3(5)
After the review of newer version 1.0.4(6), the older version does not show up in ready to publish changes.
My company has an Android app published on the Play Store since 2018. We never had any problem with the app's distribution, however since July 2020 new versions submitted and released with full rollout do not appear on the Play Store's web page or Android app - they only show an older version, published on June 2020.
We are sure that this is not a matter of caching on our end, as it is consistent across devices and platforms.
Initially, we noted that the Pre-launch report page of the Developer Console showed a few errors for these newer builds and thought that because of them the system would not release the updates, so we fixed the errors. It didn't work.
We also used to use fastlane for preparing the app's APK and uploading it, so we tried preparing the APK using Android Studio's Generate Signed APK option and uploading it manually. It also didn't work.
Our app deals with mature themes (partner swapping), but we take very good care for it to be as safe as possible. The Google Play's Developer Console shows no warning or error message for the app, so we doubt this could be the reason.
New beta and internal versions appear to beta and internal testers, but when upgraded to production, they go back to the old version from June.
No changes were made to minSdkVersion or targetSdkVersion.
I have gone through two situations and finding hard to understand the issue/working behaviour. Wish some one could help please!!
I am part of Android Beta testing program and installed the Beta build onto my device, say version 2. I was prompted to download App from Play Store which has version 1 (Version 2 is in Beta closed testing). I am quite confused with the process, higher version being prompted to download lower version. Should this be the expected behaviour and how does the flow work really?
One of my colleague was part of Android Beta testing program and had the Beta build (Version 2) installed onto his device. Later App was released to Play Store (No build exist in Beta Closed testing). Build in App Store and Beta build in Device are Version 2, but the user is Prompted to download the App on Every launch. User has deleted Beta build and downloaded App from Play Store, but still the prompt appears to download. Why is this behaviour experienced and how to avoid this issue please?
Got the issue sorted, it was to do with App itself, We have Force upgrade service in our App and was mistakenly enabled for latest version which prompted users to download on every launch.
I want to update code without going to play store and doing manually update.
So what should i do? Anyone have a idea about it
Have you increased the version code and version number in the App level gradle file. When you increase the version google play store automatically checks the installed version on your device and the version uploaded on the Google Play store. If uploaded version is greater than installed version it automatically updates the App.
Google Play has an automatic update system for apps. When a new version is uploaded to the Developer Console the app is updated on user devices because the new versionCode is greater than the one that is already installed. But users could get a newer apk from other sources.
I would like to know some details about this automatic process, I mean:
A-Does Google Play keeps a value inside so it remembers what versionCode of an app it has officially installed?
or
B-Does Google Play inspects all installed apks so it can compare the version codes to the current versions officially provided by the developers on Google Play?
Note the difference:
-in the A case, it just remember what it officially installed but is not informed about the real versionCode the user has on the device; so it could try to update even when the user already got a newer apk from outside Google Play (fail);
-in the B case, the update system can understand what version in installed because it checks it; so the update doesn't even start if the user upgraded an app from outside the Google Play.
Which is the real case?
It is case A - Google remembers which version of the app was last installed.
It does not check the device every time for the latest installed version.
How to verify this?
If you ever factory reset your phone or flash a ROM, go to play store from your browser and open an app page which you'd installed before you flashed the ROM or did a factory reset. It will still show as installed, although you wiped your device clean and it is not installed anymore.