There are a number of reasons why the error "Unable to start Mobile Inspector" would show up.
The easiest way to debug the error is to check the Logs for the Mobile Inspector. It contains the actual reason for the error.
Below given are some of the most common reasons:
1. Invalid Activity name in Manifest(Android)
The initial/default activity name mentioned in the Manifest file for the Android App might be different from the actual splash screen activity name.
For example, in case of Wikipedia Application, the initial activity mentioned in the manifest file is org.wikipedia.main.MainActivity
However, the first activity that is started when the app is launched is
Therefore, the Mobile Inspector keeps waiting for the activity mentioned in the Manifest until timeout and then throws the above error.
The ideal solution is to make the change in the manifest and mention the same Activity that is started first as the default Activity.
However, until that change is made by the developers, you can work around by mentioning the activity name and package name is the second screen 'Start manually'.