Android Studio deployment logs and raw adb exit-code visibility

Answer to the Core Question

Yes – Android Studio records the full adb install command and its exit code when a deployment fails, but only in specific log locations that are not always visible by default. The visibility is the same for APK and AAB builds: the final adb install is identical, though an AAB build adds a preceding bundletool step that may fail first.

Confirmed Facts

• When the Run/Debug configuration has Show command line enabled, the IDE’s Run tool window displays the exact adb install call and its exit code (e.g., Exit code: 1) after the attempt.
• The same command and exit code are appended to the idea.log file located in the IDE configuration directory (e.g., ~/.AndroidStudio2023.1/config/log/idea.log on Linux/Mac or %USERPROFILE%\.AndroidStudio2023.1\config\log\idea.log on Windows).
• For AAB deployments, Studio first runs bundletool build-apks and logs that output in the same command‑line section; if bundletool exits non‑zero, the adb install step is never executed. The bundletool exit code is also present in the log.
• The Build tab’s Show all output view contains the full command‑line trace, including the adb command and its exit code.
• The Event Log window only shows a short summary (e.g., “Failed to install on device”) and does not include the raw command or exit code.

How to Retrieve the Raw Evidence When the Run Window Shows Only a Summary

1. Enable Command‑Line View
   • In the Run tool window, click the drop‑down arrow next to the status line and select Show command line. The next deployment will display the full adb install call and the exit code.
2. Check the Build Tab
   • After a failed deployment, open the Build tab.
   • Click Show all output to expand the entire console trace.
   • Search for adb install – the line will include Exit code: X if the command ran.
3. Open the IDE log
   • Navigate to the configuration directory:

     # Linux/Mac
     ~/.AndroidStudio2023.1/config/log/idea.log
     
     # Windows
     %USERPROFILE%\.AndroidStudio2023.1\config\log\idea.log
     

   • Open the file in a text editor and search for adb install to locate the command and its exit code.
   • For AAB builds, also look for the preceding bundletool build-apks section and its exit code.
4. Use a Verbose Flag (Optional)
   • To force adb to emit the exit code even when the IDE suppresses it, add -v to the install command via a custom Gradle task or by editing the Run configuration’s command line. The output will contain a line like Exit code: 1.

Potential Variation Across Android Studio Releases

From Android Studio 2023.1 onward the behavior described above is consistent. Earlier releases (pre‑2022.3) may omit the exit code from the command‑line view, so the idea.log remains the most reliable source.

Missing Diagnostic Detail

To tailor the recommendation precisely, it would help to know which Android Studio version you are using. If you’re on a pre‑2023.1 release, the command‑line view might not show the exit code even when enabled.

Ask:

What exact Android Studio version (e.g., 2023.1.1, 2022.3.1) are you running?