Beta users prompted to download Public release App of Same Version - android

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.

Related

Why does release android apk are rolls back to play store version after certain time

Noticed this very strange behavior with my android application
Installed app from play store with version name 3.1 App is working
fine.
Due to new correction,I've installed App via USB connection or by
sharing apk files with same version name.
App is working fine with newly added features but
After certain time/days i found that the newly added feature is
gone and I'm using the play store version...
Additional info:
The same issue occurred in android version 11,12,9 followed by the above process.
However, I have no idea why would it is happening and how to prevent this behavior.
visited this below link for the similar issue and found nothing related to my issue.
Why does Android app rolls back to a previous version after device shutdown?
My guessing is your play store has a function that called update automatically which is opend,your apk on Phone is version behind the play store version
Found the solution for this Silly Issue.
from last one month i observed that my release apk which is not in production but has the same version name was auto updated to production version i it is for all the apk user.
I tried to disable the of google play store setting of auto update and after few day is not replaced by the production version.
:)

How to make sure that Google Play delivers the most recent version?

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

How to re-install production Android app without leaving the beta test?

I have a production version and a beta version of my app. I'm one of my beta testers. I want to rollback the version on my phone to the production version so that I can configure some settings then reinstall the beta to ensure the upgrade is working properly.
I can't seem to figure out how to re-install the production version though. I've even tried leaving the beta test and I can't get Google Play to notice that I'm not a beta tester anymore. (deleted cache and data, rebooted phone, etc).
With iOS I can install the production version from the App Store and the test version from Test Flight. How do I do that on Android?
Use different account (new google account) from Google Play to download production, then enroll in beta and try to update. this is the quickest way.
Note: you probably facing this problem because you are an internal tester and a closed beta tester too.
Toggling Developer settings helps to install the production and then switching developer settings back on gives the option to update to beta once again.
EDIT: Actually this helps only to get the change to reflect if test track is paused or resumed
Found the fix here https://android.stackexchange.com/a/245371/374079

Android Play Store installs previous version of app in Alpha

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.

Cannot upgrade old application by android studio generated apk file in Lollipop

I was installed old version(version 1) of my application from google play store in my phones. Now I would like to update this app to new version(version 2), so, I generated new apk file by using android studio and I upload this generated apk to google drive. Then download and install from my several devices(Android 5.1.1, and Android 4.2.2).
In android 4.2.2, I can install the downloaded apk and my application was upgraded to version 2 successfully.
In Android 5.1.1, I can click on install button, after that show the "App not installed" error message and the application was not upgraded to new version(version 2).
Could you please give me some advice?
Please see the attachment picture of android 5.1.1 device.
I think it is bug. It happened to me once while upgrading to a new version. The problem occurs when there are 2 users in Android OS(i.e. Settings>Users. Probably in your case, guest user must be present). So when app was previously installed, it must be installed for both primary and guest user. So when Android OS tries to uninstall the app to upgrade, it only uninstalls app for primary user and not for guest user. So the app is still present in the OS but not for primary user preventing installation of the new app. At least this is what I think it is.(I am using a Moto G)
But I have never encountered this bug when upgrading from playstore. It only happened when trying to upgrade app by installing apk from external source. I hope it helps...
When you upgrade your application and build for release, make sure that you sign your application with the same keystore you used to sign your previous application version.
When you use new keystore to sign your new application version and attempts to install it into the device with your application(old version) already installed, android will halt the installation and you can tell exactly why it does not install by looking at the logcat.

Categories

Resources