Our app had been rejected because of All File Access Permission and now we modified app compliant with google policy. We are going to upload updated version. Our app version 5.0.1 was rejected and versionCode was 51. But now I want to keep same version 5.0.1 and increase versionCode by one i.e. 52. Can I still use same versionName and increase versionCode by 1?
Yes. As #DarShan said, versionName in your build.gradle is just a label, you can arbitrarily name it. Such a restriction you mind is for versionCode. The versionCode you must set it larger number than the previous version.
defaultConfig {
minSdk 31
targetSdk 31
versionCode 1 // integer value
versionName 'Version.2021-10-28' // just a String value
}
Related
I'm trying to deploy our Nativescript app to the Google Play Store using a YML pipeline in Azure DevOps. There is a deployment task that automatically increases the versionCode and versionNumber, which always used to work fine.
However now that we upload, I get this error:
##[error]Error: Failed to upload the bundle /Users/runner/work/1/_Android/app-release.aab. Failed with message:
Error: APK specifies a version code that has already been used..
I see that the latest version in Google Play store is 1.0.3601
In the release pipeline I see that the versionCode generated is 1.0.3603 and versionName is 1.0.3604
How can this be solved? What am I doing wrong?
As suggested by User Kingston Fortune - Stack Overflow, make sure to change versionCode and versionName in build.gradle file:
defaultConfig {
applicationId "com.my.packageId"
minSdkVersion 16
targetSdkVersion 27
versionCode 2 <-- increment this by 1
versionName "2.0" <-- this is the version that shows up in playstore,
remember that the versioning scheme goes as follows.
first digit = major breaking changes version
second digit = minor changes version
third digit = minor patches and bug fixes.
e.g versionName "2.0.1"
}
References: Upload failed You need to use a different version code for your APK because you already have one with version code 2 , Problem with build version when publishing APK to Play Store , https://github.com/bitrise-steplib/steps-google-play-deploy/issues/31 and https://developer.android.com/studio/publish/versioning#appversioning
When I generate play store apk then version code is changed automatically. Here is how I define version in flavouring. How can I fix it? Any help is highly appriciated.
core {
dimension DIMENSION_APP_TYPE
applicationId "com.xyz"
versionCode 17
versionName "1.1.6"
}
26323252
I have tried to rebuild the apk 5 times with diferent number of versionCode and
versionName, like this
versionCode 8
versionName "8.0"
The application I installed on Google Play does not work on android 5 version and android 6 version. What would be the reason ?"The application is closed." error is displayed on the screen. Application Google Play Store Link : link
Gradle Code:
android {
compileSdkVersion 28
defaultConfig {
applicationId "com.frtparlak.EnglishWordTest"
minSdkVersion 16
targetSdkVersion 28
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
( A guess since no stacktrace is attached )
While you define 'minSDKVersion 16' you are still allowed to use code in your application incompatible with e.G. sdk 16.
Your compiler warns you but if you ignore these warnings and dont handle them your app will crash on some devices.
To fix it you can use the linter or just review your warnings and or your crash report.
I had uploaded these versions of my app to Google Play:
VersionCode VersionName
1 1
2 2
3 3
…
15 15
Now I plan to upload the version with
versionCode: 16
versionName: 1.6.1
Is this versionName allowed? (Or do I have to choose 16.1, so that versionNames are non-decreasing).
Is this versionName allowed?
Yes. versionName is purely to show users. It has no particular meaning to the system. You could go with Turbo System 5000 and be fine too.