Android Studio 3.0 and higher allow you to profile and debug APKs without having to build them from an Android Studio project. However, you need to make sure you’re using an APK with debugging enabled.
To start debugging an APK, click Profile or debug APK from the Android Studio Welcome screen. Or, if you already have a project open, click File > Profile or debug APK from the menu bar. In the next dialog window, select the APK you want to import into Android Studio and click OK.
Android Studio then displays the unpacked APK files, similar to figure 1.
This is not a fully decompiled set of files, though it does provide
files for a more readable version of the
The Android view in the Project pane allows you to inspect the following contents of your APK:
- APK file: Double-clicking the APK opens the APK analyzer.
- manifests: Contains the app manifests that are extracted from the APK.
- java: Contains Java code that Android Studio disassembles (into
.smalifiles) from your APK’s DEX files. Each
.smalifile in this directory corresponds to a Java class.
- cpp: If your app includes native code, this directory contains your
APK’s native libraries (
- External Libraries: Contains the Android SDK.
You can immediately use the Android profiler to start testing your app's performance.
Attach Java sources
By default, Android Studio extracts Java code from your APK and saves them as
.smali files. To debug the Java code using breakpoints, you need to point the
IDE to the
.java source files that correspond to the
.smali files you want
To attach Java sources, proceed as follows:
- Double click on a
.smalifile from the Project pane (use the Android view). After opening the file, the editor displays a warning banner asking you to select the Java sources, similar to what's shown in figure 1.
- Click Attach Java Sources from the banner at the top of the editor window.
- Navigate to the directory with the app’s Java source files and click Open.
In the Project window, the IDE replaces
.smali files with their
.java files—The IDE also includes inner classes automatically.
You can now add breakpoints and debug your app as
you normally would.
Attach native debug symbols
If your APK includes native libraries (
.so files) that don't include debug
symbols, the IDE shows you a warning in the Messages window, similar to
the one shown in figure 1. You can not debug the APK’s native code or use
breakpoints without attaching debuggable native libraries.
To attach debuggable native libraries, proceed as follows:
- If you haven't already done so, make sure to download the NDK and tools.
- Under the cpp directory in the Project window (visible only if you've selected the Android view, as shown in figure 2), double-click a native library file that doesn't include debug symbols. The editor shows a table of all the ABIs your APK supports.
- Click Add at the top right corner of the editor window.
- Navigate to the directory that includes the debuggable native libraries you want to attach and click OK.
If the APK and debuggable native libraries were built using a different workstation, you need to also specify paths to local debug symbols by following these steps:
- Add local paths to missing debug symbols by editing the field under the Local Paths column in the Path Mappings section of the editor window, as shown in figure 2. In most cases, you need only provide the path to a root folder, and Android Studio automatically inspects subdirectories to map additional sources. The IDE also automatically maps paths to a remote NDK to your local NDK download.
- Click Apply Changes in the Path Mappings section of the editor window .
You should now see the native source files in the Project window. Open those native files to add breakpoints and debug your app as you normally would. You can also remove the mappings by clicking Clear in the Path Mappings section of the editor window .
Known issue: When attaching debug symbols to an APK, both the APK and
.so files must be built using the same workstation or