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.
:)
The situation
An app is released to Google Play as apk. First release back in 2018, several apk updates since. Now as is required from Google (pr. August / November 2021), the format needs to be app-bundle instead of apk when updating the app.
I successfully build the app-bundle and uploaded to Google Play Console. I released the build on 'internal test' track. All seems to be just fine.
The problem
However, no matter what I do, I keep seeing and downloading the latest apk-version instead of the new app-bundle version.
The latest apk version-code is "400126/200126" (x64/x86).
The latest app-bundle version-code is "131".
I first thought it could be a problem that 131 < 400126 (obviously), so I created a new release on the 'internal test' track without any artifact - in the hope that could sort of 'reset' the state - and then creating a new release with the "131" app-bundle again. However no luck in getting the app-bundle version on my devices.
Besides I tried these things with no luck
Unsubscribing and re-subscribing the 'internal track' a dozens of times.
Removed and re-added my Google-id email from the set of 'testers' on Google Play a dozens of times.
Cleared the Google Play cache on my devices.
Installing from Web a dozens of times. Always ending up getting the latest apk-version installed. But actually, when entering my App on Google Play Web, it still shows the latest apk-version, even though it tells me (correctly) that this is a beta-version (indicating that I, indeed, is registered as internal tester). This, at least, is consistent with the fact that I keep download and finding only the latest apk in Google Play app on my phone-device, and not the app-bundle.
BUT! How do I get my new app-bundle available on the 'internal test'? All suggestions are more than welcome. Thanks!
I ended up creating a ticket at Google Support. They quickly replied that I simply needed to increase the build-number to > 400126. That makes a lot of sense.
However, we had another app where this was not needed - but that might be because the app had not yet been promoted to production at the time?
I already had a version (versioncode=2) in Google Store. Yesterday after doing some changes, when I tried publishing the app, i am getting below error message and not able to publish the updates. Any idea how can I fix it?
This configuration cannot be published for the following reason(s):
Version 2 is not served to any device configuration: all devices that might receive version 2 would receive version 3.
Some devices are eligible to run multiple APKs. In such a scenario, the device will receive the APK with the higher version code.
FYI, the new version is versioncode=3
You need to "Deactivate" the current apk in order to actually publish the new apk.
Deactivate the 2 version on the Google Play.
All this says is that version 3 is applicable for all devices that version 2 is applicable for. This means version 2 is obsolete.
If you check closely, when you upload your APK there is no option to Publish to production, only Save as Draft. This happened to me last night and drove me crazy. Now, in the morning I uploaded the new APK again and the Publish to production button was there! I don't what caused this issue but now it's fine.
I have updated new version of apk on Google Play. But still in statistics I see people downloading older version, how is that possible ? Has anyone encountered this problem ?
Regards
Are the new APK's requirements the same as the old one? It can come from there.
For example, let's say the old APK's minSdkVersion is 8, and the new one is 9. Then users with SDK version 8 will still be able to download the old APK.
As minipif has said, you may have changed minSdkVersion in your manifest, or some other attribute e.g. supports-screens.
If this results in you decreasing the number of devices supported in your new apk then, by default, Google Play will keep hold of the old apk and deliver it to devices not supported by the new apk (but supported by the old apk).
You can override this by simply unpublishing your old apk in the developer console.
Whether you replaced that with older apk by switching to new apk update?
If yes, it takes couple of hours to update in android market.
Play Store app has cache. You can delete cache from settings.
I got it. This is because mobile app stores cache. If you go to GOOGLE APP -> My Apps -> ALL and install from that cache it will also download and install the apk which u unpublished long back in past. Big bug in Google....PHEWWWWWWWWWW...
I'm trying to publish a new version of my Android app to Google Play and get the following error?
This configuration cannot be published for the following reason(s):
Version 1 is not served to any device configuration: all devices that might receive version 1 would receive version 4
I don't understand it. What does it mean?
This happened to me when I published two APKs (versions 3 and then 4) in a short space of time. Clicking "Deactivate" on the dropdown next to version 3 appeared to fix it.
My guess is that this is a very-poorly-worded error message meaning something like "your original APK hasn't been published to all the update servers yet, so some of them may miss that version entirely". But it's a bit of a guess.
For some reason when you upload a new APK without immediately clicking "publish" (you probably clicked save draft the first time), Google thinks you want to publish BOTH apk at the same time.
This is usually needed when you have multiple APK for different configuration (say: a version for android 2.x and another for 3+ or a version for tablet and another for handset etc...)
However in your case you are just uploading an upgrade and you want it to replace your previous APK.
To solve:
Click on the Switch to Advanced Mode on the top right
Click on Action -> Move on the OLD APK and choose "Deactivate"
The error should go away and you should see your OLD apk in "OTHER APKS" and the new one ready to be published.
Just click Publish to make your change effective and wait for them to propagate.
The Google warning is missleading.
Hope this clarify it.
I have solved the same problem with my app. I must upload from version 1.0 to the version 2.0.
- I have uploaded the v2.0 in Beta.
- When it was uploaded, I have DEACTIVATED the v1.0 in the PROD.
- Next step was to MOVE the v2.0 to PROD from the BETA.
- Then, the PUBLISH button was activated to finish the process.
I hope it helps.!
The solution of #Chris is right. But what the message really means is:
version1 and version4 has the same configuration: same API level, same screen resolution... bascially everything in manifest...
So this means any device can install version can install version4, too.
Now everything is clear: since version4 has higher versionCode, every devices will recieve the version4 instead version1.
There's no meaning still put version1 "in production" anymore. Under no circumstance any device would recieve this version. So you should "deactivate" it.
This may be a hack, but you can workaround this by doing staged rollout to 1-50%, then increase it to 100%.
This case the error message does not prevent publishing your app and also you don't have to deactivate anything.
This is purely a guess but do you have a previous version uploaded? If so it might be that it's marketcode is set to something higher than your new build e.g. 4
I had a similar problem, but because my previous version had a lower maximum andorid api, I was not allowed to revert to previous version.
In the end for me it was a problem wit eclipse that was not saving the change to the manifext file. I restarted eclipse, saved my project, made an apk and then it worked. Maybe worth a try if the above answers fail.
I just switched to the basic view. Which automatically replaces the current version with the new version immediately. That is of corse not suitable for every app deployment scenario. But should be all right in most (simple) cases.
You can only have one APK in production at a time. Before uploading you must deactivate the current one. The same goes for alpha and beta test APKs combined - you can only have one APK published for testing.
I agree the wording of the error message is appalling!
I had the same issue, but I executed following command on my APK file
jarsigner -verify -verbose -certs Myapp.apk
then I uploaded the new APK on the play store and it published easily.
I guess the console is telling your that u have two versions supporting the same devices so there is no reason to be using both
solution: remove the older one...
OR
if ur older version supports specific devices, mark that and the console will accept it
I also received that problem when I uploaded the APK at the first time but I noticed that API level 18-17 when viewing APK details. Therefore, I added this code to AndroidManifest.xml to specify the maximum API level
<uses-sdk android:minSdkVersion="18"
android:targetSdkVersion="23"
android:maxSdkVersion="23" />
After doing this, the problem is solved :)
in my case
an older version of apk was published in beta testing. while i was trying to update my app over already published app with new apk.
just moved my new apk to beta testing and unpublished the old apk from beta testing.
and then finally moved the new apk from beta to prod.
I had the same problem i just DEACTIVATE the old apk which was currently active and then upload new apk. IT SOLVED my Problem
To resolve the issue, do the following:
delete the new apk that is in the draft mode
clear the history cach of the browser or use other browser and re-upload the apk
I had the same issue, but I resolved by Block Lint Errors.
See the Lint Error page, right corner packager icon, click there and block package.
When you click for leaving lint error, the application make export singed application package.
it happened to me, when I published new APK, but accidentally closed browser window without finishing submission.