I have an Android app in alpha testing; I have uploaded updated APKs a few times. My testers report that they still get the previous version, not the latest one, even though the Developer Console says the latest version is the right one - the latest I uploaded a few days ago - and doesn't say "Processing update" any more.
Is there anything I should advise my testers to do on their devices, and can I do something at my end?
I couldn't install the latest public version of an app either, even after the alpha testing program for that app was ended. Then I manually left the testing program by going to the link where had I registered as a tester in the beginning.
In my app's case, the link was
https://play.google.com/apps/testing/np.com.naya.pasal
Mind to put your app id instead of np.com.naya.pasal in the above link
Your testers will get message like this when they have left the test. After a while they can install the latest version.
If you want to install old version of the app, then
Uninstall the app if you have already installed.
Then go to Google Play console > App bundle explorer. From there select app version and there you can see Shareable link to the app in Downloads tab. From that link you can install that specific app version.
Related
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
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 have submitted an update to my Android app on the Google Play Console and it was approved, and shows newest version on Google Play Store.
However, when I download app on Play Store, the old version APK is what is downloaded, not the new version.
I have tried clearing Play Store cache, as well as uninstalling and reinstalling app, but still old APK. This is troubling because it shows that I am downloading the newest version.
Has anyone else had this issue?
Thanks
There are a few things you can do to check. The first is look at the version code of the app you are downloading. If you are the developer of the app, using adb you can pull the app off the phone using:
adb shell dumpsys package my.package | grep version
The version code is the definitive thing that will tell you if the new version of the app is on your phone. If the version code is the new version, but the code seems to be doing the old thing, then you made a mistake when submitting your APK.
If the version code is the old version, then a few things could have happened:
The Play store has to update lots of different caches in different data centers around the world, and this can take a little while. Try waiting 15 minutes and seeing if things get better.
You could have accidentally left your old version of your app live, and the old version is compatible with your phone, but the new version isn't.
this could really be a bug with Play. If so, use the "contact us" link on this page, and they might be able to look at your account and see the problem
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.
My app is already published.Now I wish to update it with newer version,But I did some serious changes so I wish to check it first in alpha version.
I uploaded my apk with next version in alpha,It is completely 24 hours,But still now It is not showing in playstore,In playstore my old app version is present.
I have logged in with tester-id which I have added to google-group(tester).
I am not trying to download old apk,
But trying to download the apk which I have uploaded in alpha testing.
the app which is in production have version 6.
and I uploaded version 7 in alpha testing.when I am opening the tester link with tester id,I expect it should show me my app with latest version(ie. version 7).
But still it showing version 6.
Can any one tell me how do I download it,As I am not able to find it?
I found solution, you cant find your app using search box, you can use generated direct link only.
link