Alpha test download link downloads differents versions of the application to testers. The version number of the downloaded application is the lastest one but it is missing some functionalities that are in the latest version that I published.
So we tried again to download the latest version of the application through the Internal Testing and Internal app sharing of Google play but we are encountering the same issue.
Has anybody encountered the same issue? Can you assist?
Thank you.
Related
I am using Google play store Managed publishing feature. I have multiple app versions as below in the "Changes ready to publish" state in the Google Play console. I would like to only publish v6.6.1 as staged rollout, but I wonder if v6.6.0 will also be published when I publish the releases. I dont want v6.6.0 to be pubished, would prefer if it could be deleted but there was no way to remove an approved release.
Any assistance is much appreciated.
Option 1:
I think this could be done by going to Google Play Console and select App bundle explorer from the left menu.
then chose the App version 6.6.0 click on Upload new version
you should upload a version that is identical to the version previous to 6.6.0 but with same 6.6.0's version code & same version name (6.6.0).
Note: I've never tried this before, but I noticed it in the new Google Play Console.
Option 2:
upload a new version that is identical to the version previous to 6.6.0 but with new version code (highest version code, higher than 6.6.1 version code) and version name 6.5.9 (for example)
submit it as full roll-out
upload a new version that is identical to the version previous to 6.6.1 but with new version code (highest version code, higher than 6.5.9 version code) and version name 6.6.1 with Staged roll-out = 1%
I'm making a Java program which will be deployed to the Google App Engine and I'm using the Cloud SDK maven plugin version 2.4.0 to deploy to the GAE. However when I run mvn package appengine:deploy the cloud SDK will say its current version is 321.0.0 and needs to update to 327.0.0. The update will then fail with the error:
ERROR: (gcloud.components.update) Access is denied: [C:\Users\jamie\AppData\Local\Google\ct4j-cloud-sdk\LATEST\google-cloud-sdk.staging\platform\kuberun_licenses\LICENSES.txt]
However when I just run gcloud components update I get the result of All components are up to date.
Anyone know why this may be happening or how to fix it?
EDIT: As a work-around I found you can force the maven plugin to use a specific version of the sdk by using <cloudSdkVersion>321.0.0</cloudSdkVersion>. I'm still very curious to know why this occurred though
Manged to fix this by deleted the whole C:\Users\jamie\AppData\Local\Google\ct4j-cloud-sdk folder as this forces the plugin to redownload a fresh SDK.
The error occurs as the plugin uses its onw auto managed SDK rather than the one which is user managed.
I have published two versions of my app apks to Google Play Console.(1.3, 1.4)
But later I realised that there is a minor issue in my newest version(1.4) that I have uploaded. So now I need to un-publish the newest version(1.4) and publish the older version(1.3) again.
How can I do that?
This was already answered here:
https://stackoverflow.com/a/29549730
It's not possible. You'll have to rebuild the older state and upload again under a new version number.
Well we released an update for our app last month, that set the minSDK to 5.0. We did this because we had a server side change that would break those on below 5.0.
Is there anyway to release another app on Google Play that would only be for user on below 5.0?
If we were to release the 5.0 and below version for a few days and then release the 5.0 and above. Will the 5.0 and below user still see that "slightly newer" below 5.0 release?
Yes. This is known as "multi-APK". See this help page.
You have two options for making sure users get the right APK.
the simplest to understand option is to set maxSdkVersion in the manifest of your pre-5.0 APK, and minSdkVersion in your manifest for the post 5.0 APK.
another option to use version code. Google Play will always deliver the highest version code that is compatible with a user. So if you make sure your pre-5.0 APK always has a lower version code than your post-5.0 APK, then both types of users will get the correct APK.
I ran into an issue today where my preview server was running an older version of a project instead of the most recently published version. The most recently published version was 1.0.4.10, but after some testing, I determined that version was not the version of the application that the server was retrieving.
After trying a few things, I tried publishing a new version under 1.0.5.0 instead of continuing with the 1.0.4.xx numbering, and that fixed the issue.
VS's auto increment feature recommended 1.0.4.10, but is there an issue with this being the same as 1.0.4.1? So maybe it was running 1.0.4.9? Or something behind the scenes I'm not aware of?