When developing mobile applications for the Android platform, it is critical to control the environment in which you you are working. Knowing the exact build number of the integrated development environment (IDE) is necessary for correct configuration of plugins, compatibility with Gradle, and elimination of compilation errors. Often, developers are faced with a situation where functionality does not work due to a mismatch between the versions of tools or plugins.
There are several reliable ways to determine the current build of the app, from the standard "About" menu to checking system files.
The choice of method depends on whether you are currently running a development environment or need to find out information about the installation file on disk. In this article we will analyze all the available diagnostic options.
Checking through the main menu of the app
The most obvious and fastest way to find out information about the product is to use the built-in interface. If the app is already running and working correctly, you will not need to search for hidden files or launch a terminal.
Depending on the operating system of your workstation, the location of the menu item will differ. macOS users should click on the Apple logo in the upper left corner of the screen, then select the application name Android Studio and item About Android Studio.
In the Windows or Linux operating system, the path is slightly different. You will need to open the menu Help in the top toolbar and select the option About. A modal window will open containing the logo, build number, and license information.
⚠️ Warning: If the menu item is grayed out, it may mean that the input focus is not in the main IDE window, but in a third-party plugin or dialog box. Close all pop-up windows and try again.
In the window that opens, you will see not only the version number, but also the Build number, which looks like a combination of letters and numbers, for example, AI-232.10300.40.2321.1234567. This code is often required when contacting technical support or searching for solutions on forums.
Remember or write down the Build number, since the version number (for example, 2023.2.1) can be the same for different patches, and the build is unique for each update.
Using the Settings and Properties window
An alternative method of obtaining data about the development environment is through deep system settings. This method is useful if the standard "About" menu is unavailable for some reason or the interface is damaged.
Go to the settings section using the key combination Ctrl+Alt+S for Windows/Linux or Cmd+, for macOS. In the window that opens, on the left side, find the section Appearance & Behavior, and then the subsection System Settings.
Although update settings are most often displayed here, in some configurations and versions of the interface information about the current state of the system is duplicated. A more reliable way in this context is to use the window Properties for the launch shortcut if you are working on Windows.
- 🔍 Right-click on the shortcut on the desktop.
- 📜 Select "Properties" in the context menu.
- 📂 Go go to the "Details" tab (if available) or look at the target.
However, the shortcut properties may show the installer version, and not the current version of the app after internal updates. Therefore, this method is considered auxiliary and less accurate compared to checking inside a running application.
Analysis of the gradle.properties configuration file
For professional developers working with the Gradle build system, matching the IDE version and the Android Gradle plugin version is critical. Sometimes the environment itself can be updated, but the project settings require manual adjustments.
Information about the required or used version of the tools can be found in the file gradle.propertieslocated in the root of your project or in the global directory .gradle.
Open this file in any text editor. Find the line starting with android.injected.invoked.from.ide or parameters associated with the plugin version. While this does not always show the version of the studio itself directly, it does provide an understanding of the compatibility context.
org.gradle.jvmargs=-Xmx2048m -Dfile.encoding=UTF-8android.useAndroidX=true
android.enableJetifier=true
A more accurate indicator is a file .idea/misc.xml inside the project folder. When you open it, you will find a tag component name="ProjectRoot", where the language level and other parameters may be indicated that indirectly indicate the requirements for the IDE version.
⚠️ Attention: Gradle configuration files may differ in different projects. Do not copy plugin version settings from an old project to a new one without checking the documentation, this may lead to synchronization errors.
Why do the versions not match?
Often the version of Android Studio is higher than the version of the Gradle plugin supported by the project. In this case, the IDE will offer to update the plugin when opening the project.
Checking via the command line and terminal
For experienced users who prefer working with the console, it is possible to obtain version information without launching the graphical interface. This is especially true for server environments or when writing automation scripts.
If the path to the executable is added to your operating system's environment variables, you can call up help directly from the terminal. The command may vary depending on the OS.
On Linux or macOS, try running a command that points to a binary file inside the application package. On Windows, this can be done via PowerShell by accessing the executable studio64.exe with the version key.
- 💻 Open a terminal or command line.
- 🚀 Enter a command to check the version of the executable.
- 📋 Analyze the output system.
It is worth noting that the standard flag --version does not work for all Android Studio shortcuts, since this is not a console utility. Most often, this method requires directly accessing the binary in the installation folder.
Directly calling the binary file from the console is the least convenient, but most reliable way to check the integrity of the installation if the graphical interface does not start.
Viewing information in the installation folder
If the app does not start, the only way to find out its version is to refer to the file system. The installation directory stores manifest and configuration files containing metadata about the product.
In the Windows operating system, the default path looks like C:\app Files\Android\Android Studio. Inside this folder, find the file build.txt or product-info.json.
Open the file build.txt using Notepad. It will contain one line with the assembly code, for example AI-232.10300.40.2321.1234567. You can decode this number into a clear version (for example, Hedgehog, Giraffe) by checking the official correspondence table.
| Code name | Version (example) | Year of release | Features |
|---|---|---|---|
| Hedgehog | 2023.1.1 | 2023 | Improved profiler |
| Giraffe | 2022.3.1 | 2023 | Wear OS support |
| Flamingo | 2022.2.1 | 2023 | New UI inspector |
| Electric Eel | 2022.1.1 | 2022 | Updated emulator |
On macOS, the application is a package. Right-click on the icon Android Studio in the Applications folder, select "Show package contents". Then go to Contents and open the file Resources, where information about the build is often located.
⚠️ Attention: Do not edit the files in the installation folder manually. Changing files.txtor.jsoncan break the digital signature of the application and lead to a refusal to launch.
☑️ Diagnosing a launch problem
Frequently asked questions about Android Studio versions
Developers often ask questions about compatibility and updates. Below are answers to the most popular queries related to development environment versions.
Is it possible to install two versions of Android Studio at the same time?
Yes, you can install different versions in parallel. When installing a new version, the wizard will suggest not to delete the previous one, but to install it side by side. This allows you to test projects in different environments without conflicts.
Why does the build number not match the version on the site?
The number on the site usually indicates a stable release (Stable), while you may have a Canary or Beta version installed. It is also possible that you missed the automatic update of the security patch.
How to roll back to a previous version of the IDE?
Officially, the rollback function is not provided. You will need to uninstall the current version, download the required installation file for the previous release from the archive and install it again. Settings can be restored from a backup.
Does the Studio version affect the size of the APK file?
The IDE version number itself does not affect the size of the application. However, new versions may include more efficient resource compression algorithms (R8) or offer new libraries, which can indirectly change the final size of the binary.