Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 558956]
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
If the Universal C Runtime is not installed, executing "adb.exe" programmatically (via the Java java.lang.ProcessBuilder API) results in 1) no output and 2) a process exit value of 0xc0000135 (STATUS_DLL_NOT_FOUND).
The current implementation of com.android.ddmlib.AndroidDebugBridge.getAdbVersion() does not check the process exit value, so we end up with a very generic error message ""Unable to detect adb version, adb output: " (not the output is empty). This is not actionable from an end-user perspective.
The proposal for this bug is two-fold
1) If the process exit value is non zero, add that information to the error message.
2) If running on Windows and the exit value is 0xc0000135, add a message to the error message advising users to install the Microsoft Universal C Runtime. (and point to the URL).
Message: There was an error starting the ADB process. Please check the Universal C Runtime for Windows is installed.
URL: