This is quite strange situation. I have an android app in the market. Current version is 1.5.1 uploaded on 18th June. Google play is also displaying as last production release. This release has version code 25. yesterday I wanted to do another upload with version code 26 but I only saved as draft.
But google play shows me a notification that my release is live in the store
This release had 1.6 as release name but in the store is still 1.5.1. So I wanted to do another release with 1.6. now it tells me that "You need to use a different version code for your APK because you already have one with version code 26". I dont have this release draft also. It doesn't even appear anywhere. it is not also live in the store.
Does anybody have something similar? is it safe to make a new release with code 27 now? because Last release in the market is 25. so I will skip 1 number. will users receive update?
Yes, it's best to go change your version code to 27. Yes, users will receive the update.
If you can't find it, go to the build.gradle and set the version code and name inside the defaultConfig element
defaultConfig {
minSdkVersion 9
targetSdkVersion 19
versionCode 1
versionName "1.0"
}
You can then upload it. Google only checks the gradle file to manage versions. But the users' client devices have no check. They will update it if the option is checked.
Related
I have an existing app in the play store which is in APK format. I created the next release as .aab. When I uploaded the file, the play console shows the message that the release will stop support for over 1000 devices. How can I reduce this number?
minsdk 19
targetsdk 28
I would also like to mention that I have not edited the build.gradle since the last release. Really appreciate any help.
I read that if we want to update an app in google play, the version Code should be higher than the previous apk file. I've an app with version code: 20 and version name 1.0. So to update the app, how should I increase the version code? Should it increase by 10? or just 1 is enough? ie, version code from 20 to 30 or version code from 20 to 21?
VersionCode
This number is used only to determine whether one version is more
recent than another, with higher numbers indicating more recent
versions. Typically, you would release the first version of your app
with versionCode set to 1, then monotonically increase the value with
each release, regardless whether the release constitutes a major or
minor release. This means that the versionCode value does not
necessarily have a strong resemblance to the app release version that
is visible to the user (see versionName, below). Apps and publishing
services should not display this version value to users.
defaultConfig
{
minSdkVersion 17
targetSdkVersion 23
versionCode 1 // Default , You can increase 1 when update .
versionName "1.0"
}
You can use the Play Core Library In-app updates to tackle this. You can check for update availability and install them if available seamlessly.
In-app updates are not compatible with apps that use APK expansion files (.obb files). You can either go for flexible downloads or immediate updates which Google Play takes care of downloading and installing the update for you.
dependencies {
implementation 'com.google.android.play:core:1.5.0'
...
}
Note that, In-app updates works only with devices running Android 5.0 (API level 21) or higher, and requires you to use Play Core library 1.5.0 or higher.
'
I hope this will help somebody
I increased it from code 1 and version 1.0 to code 2 and version 1.1 . That's also what it says in my developer console. So just do as you wish
Basically, For update your apk you should update version code to 21(just 1 increase) and your version name.
I've been facing a serious problem lately with Android Studio, where the versionCode specified in the build.gradle file is not taken into account.
It happened twice now, and the first time it just worked for no reason after countless tries. It's either this or the Google Developer Console has some sort of bug which doesn't correctly detect the versionCode.
I tried editing it manually as well as with the build flavors, I always get an error message from Google when trying to upload the update, specifying the old versionCode.
(I am also changing the versionName)
You have to update both versionCode & versionName to higher values
I want to know suppose I upload a new app on Google Play with minSDKVersion to 14 with Version 1 and then later I want to make it compatible to Android 2.3+ so I will set the minSDKVersion to 9 in Version 1.1
Is this possible or Google Play does not allow you to decrese the value of minSDKVersion in updates release ?
Thanks in advance.
Yes, it is possible.All you have to do is increment your app's version code.
As far as I know you dont need to do anything in google play developer console, just modify the minSDKVersion in the manifest and use a higher version code
How set the android max sdk version on build.gradle at android studio.
I want do an app with two flavor, the first will run between version x~y and the second run at y+
Before on eclipse, in AndroidManifest.xml we have android:maxSdkVersion="y" but how it works on gradle?
You cannot set the maxSdkVersion in gradle. Actually, it is discourage by Google because of several issues. The main issue is that Google Play could decide to remove an app from a user device during an update if the system doesn't meet the maxSdkVersion specified in the app. For example, imagine you have a device with API Level 12 and you install an app with android:maxSdkVersion="12", then later you receive a system update that upgrades your android version to API Level 13...Google Play will uninstall your app.
Basically, you don't need this setting and you can easily ignore it, use the targetSDkVersion attribute and the minSdkVersion.
For your app "in flavour 1" with "version x~y" set the minSdkversion to x and the targetSdkVersion to y
now, for the app "in flavour 2", you will need to make sure that the sdk version don't get overlapped by the app "in flavour 1", set the min sdk version to "z". Otherwise, users with a device with api level "y" will never get to see this app in Google Play
Please note this.
Future versions of Android (beyond Android 2.0.1) will no longer check or enforce the maxSdkVersion attribute during installation or re-validation. Google Play will continue to use the attribute as a filter, however, when presenting users with applications available for download.
https://developer.android.com/guide/topics/manifest/uses-sdk-element.html
I think accepted answer is not correct. Accepted answer says it is not possible to set maxSdkVersion - it is not true. It is still possible to use maxSdkVersion in android studio app/build.gradle. As described here https://developer.android.com/guide/topics/manifest/uses-sdk-element developer must notice warning and should understand why wants to do it. Nobody here take care that in play store you can provide several bundles/packages at once (per update/release) and one bundle can be targeted for new devices and another for old devices so it is fine second one limit by maxSdkVersion. One app bundle have versionCode e.g. 2xyz and for older devices is versionCode 1xyz and google always installs higher code when minSdkVersion allows it. So developer can purposely set maxSdkVersion and he know why hi is doing it.
Each our app update have 2 packages with different app/build.gradle...
For old devices
(maxSdkVersion has sense here)
defaultConfig {
minSdkVersion 16
maxSdkVersion 23
targetSdkVersion 30
versionCode 1058
versionName "4.4.0"
}
For new devices
(without limiting maxSdkVersion as googole warns that should not be used)
defaultConfig {
minSdkVersion 24
targetSdkVersion 30
versionCode 2058
versionName "4.4.0"
}