Android version name string

How to get the versionCode and versionName of your app

EnvyAndroid

Read more posts by this author.

EnvyAndroid

In you AndroidManifest.xml file, you can specify the values of android:versionCode and android:versionName .

versionCode

The versionCode is integer value used to easily differentiate between app versions.

App developers must increment this value when they release updates to their apps in Android Market, so it can determine if users are using an old version of the app, and offer them to update it.

versionName

The versionName is a string containing a regular “release version” as seen in other desktop applications, such as “1.4.5” or “3.7”.

The versionName is just a “human readable” version code.

Accessing it

Here is how you can access these values in your application code:

This way, you can check which version of your app is being used, if you need to do something spesific with that information. Or you can make a small method that checks for new updates to the app.

You can also access other useful resources this way, for example: packageName and requestedPermissions.

More on android app versioning here, and AndroidManifest i explained in depth here.

Источник

Manage your Android app’s versionCode & versionName with Gradle

Don’t repeat yourself. Specify app version metadata just once.

Dec 28, 2015 · 3 min read

Gradle, which is now Android Studio’s default and recommended build system, can help you automate many tasks that other developers might be doing manually.

As you know, every Android app must declare an app’s versionCode (a monotoni c ally increasing integer for each version of the app), and versionName (a text description which can really be anything, but is usually a human-readable version string of the form x.y.z (major version, minor version, patch level). An app’s versionName is usually shown within the app in the About screen, and in other places, such as when sending a bug report. Here’s how you can specify everything in exactly one place and use it everywhere needed.

Define individual components of the version number.

Start off with defining individual components of the version number—major version, minor version and patch level—as separate Gradle variables. This is the one place you’d update the numbers for every version you release.

Compute values for versionCode and versionName.

Then have Gradle compute the versionCode from these three components as a place-value-based number. The versionName is a straightforward string concatenation of the three components.

This will, for example, assign a version code of 20401 for an app with version 2.4.1. That gives you the possibility of 100 minor versions for every major version, and 100 patch levels for every minor version. Seems enough, right?

Generate a string resource.

Next, have Gradle generate a string resource for you automatically, which you can use in your about app’s XML layouts & Java code (as @string/app_version & getResources().getString(R.string.app_version) respectively).

Identify your debug releases.

The code snippet above adds “.debug” to the versionName of all debug releases, so if you see one of these in your logs, you’ll know this wasn’t a release that your users saw — phew! The resource value isn’t automatically updated when we add a versionNameSuffix, so we handle that separately for the debug build type.

Check your generated AndroidManifest.xml.

Now if you look at your generated AndroidManifest.xml, you’ll see that it has the correct auto-generated versionCode and versionName. Note, this is under the build/ directory, not the one in your app/ directory.

Show the version in your About screen.

If you use a Preference-based About screen, simply use the generated string as the preference value.

Источник

How to find the Android version name programmatically?

I write code for finding the Android version like this

by using this code I am get the version number but I want version name. how to get the version name?

14 Answers 14

As suggested earlier, reflection seems to be the key to this question. The StringBuilder and extra formatting is not required, it was added only to illustrate usage.

On my 4.1 emulator, I get this output:

Optimized code, this will work:

After API 28 (Android Pie), Build.VERSION_CODES were changed some fields.

So, if you using:

will cause your app crash immediately because of Out Of Range Exception.

The solution for all API level is:

Or in Kotlin with Java 8’s style:

http://developer.android.com/reference/android/os/Build.VERSION_CODES.html contains fields that have the name you’re looking for. So you could use reflexion to find which field corresponds to the «version» value.

Why do you want the name ?

You will get the information from these

More information can be had from this link:

Hope this will help you.

Be aware that this solution will only work as far as the version codes keep being incremented by one, and you will have to update the list with each new android version (if being accurate is important).

As described in the android documentation, the SDK level (integer) the phone is running is available in:

The enum corresponding to this int is in the android.os.Build.VERSION_CODES class.

Edit: This SDK_INT is available since Donut (android 1.6 / API4) so make sure your application is not retro-compatible with Cupcake (android 1.5 / API3) when you use it or your application will crash (thanks to Programmer Bruce for the precision).

Источник

versionCode vs versionName in Android Manifest

I had my app in the android market with version code = 2 and version name = 1.1

However, while updating it today, I changed the version code = 3 in the manifest but by mistake changed my version name to 1.0.1 and uploaded the apk to the market.

Now, will the users of my app get an update notification on their phones or not? Or should I redo the process again?

11 Answers 11

android:versionCode

An internal version number. This number is used only to determine whether one version is more recent than another, with higher numbers indicating more recent versions. This is not the version number shown to users; that number is set by the versionName attribute. The value must be set as an integer, such as «100». You can define it however you want, as long as each successive version has a higher number. [. ]

android:versionName

The version name shown to users. This attribute can be set as a raw string or as a reference to a string resource. The string has no other purpose than to be displayed to users. The versionCode attribute holds the significant version number used internally.

Reading that it’s pretty clear that versionName is just something that’s shown to the user, versionCode is what matters. Just keep increasing it and everything should be good.

Dont need to reverse your steps. As you increased your VersionCode, it means your application has upgraded already. The VersionName is just a string which is presented to user for user readability. Google play does not take any action depending on VersionName.

Version Code — It’s a positive integer that’s used for comparison with other version codes. It’s not shown to the user, it’s just for record-keeping in a way. You can set it to any integer you like but it’s suggested that you linearly increment it for successive versions.

Version Name — This is the version string seen by the user. It isn’t used for internal comparisons or anything, it’s just for users to see.

For example: Say you release an app, its initial versionCode could be 1 and versionName could also be 1. Once you make some small changes to the app and want to publish an update, you would set versionName to «1.1» (since the changes aren’t major) while logically your versionCode should be 2 (regardless of size of changes).

Say in another condition you release a completely revamped version of your app, you could set versionCode and versionName to «2».

Hope that helps.

You can read more about it here

Version code is used by google play store for new update. And version name is displayed to the user. If you have increased version code then update will be visible to all user.

For more detailed inform you give 2 minute reading to this article https://developer.android.com/studio/publish/versioning.html

I’m going to give you my interpretation of the only documentation I can find on the subject.

«for example to check an upgrade or downgrade relationship.»

android:versionCode — An integer value that represents the version of the application code, relative to other versions.

The value is an integer so that other applications can programmatically evaluate it, for example to check an upgrade or downgrade relationship. You can set the value to any integer you want, however you should make sure that each successive release of your application uses a greater value. The system does not enforce this behavior, but increasing the value with successive releases is normative.

android:versionName — A string value that represents the release version of the application code, as it should be shown to users.

The value is a string so that you can describe the application version as a .. string, or as any other type of absolute or relative version identifier.

As with android:versionCode, the system does not use this value for any internal purpose, other than to enable applications to display it to users. Publishing services may also extract the android:versionName value for display to users.

Typically, you would release the first version of your application 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 android:versionCode value does not necessarily have a strong resemblance to the application release version that is visible to the user (see android:versionName, below). Applications and publishing services should not display this version value to users.

Источник

Get Android .apk file VersionName or VersionCode WITHOUT installing apk

How can I get programmatically get the version code or version name of my apk from the AndroidManifest.xml file after downloading it and without installing it.

For example I want to check if a new version is uploaded on my IIS service, after install it on device, if it is not a new version I don’t want to install it.

10 Answers 10

Following worked for me from the command line:

NOTE: aapt.exe is found in a build-tools sub-folder of SDK. For example:

If you are using version 2.2 and above of Android Studio then in Android Studio use Build → Analyze APK then select AndroidManifest.xml file.

This answers the question by returning only the version number as a result. However.

The goal as previously stated should be to find out if the apk on the server is newer than the one installed BEFORE attempting to download or install it. The easiest way to do this is include the version number in the filename of the apk hosted on the server eg myapp_1.01.apk

You will need to establish the name and version number of the apps already installed (if it is installed) in order to make the comparison. You will need a rooted device or a means of installing the aapt binary and busybox if they are not already included in the rom.

This script will get the list of apps from your server and compare with any installed apps. The result is a list flagged for upgrade/installation.

As somebody asked how to do it without using aapt. It is also possible to extract apk info with apktool and a bit of scripting. This way is slower and not simple in android but will work on windows/mac or linux as long as you have working apktool setup.

Also consider a drop folder on your server. Upload apks to it and a cron task renames and moves them to your update folder.

Источник