Mostly manual sideloading of apps can be avoided by uploading the target app to an ftp server or file server and downloading using the Emulator browser. There are however some special cases where the app can not be downloaded, usually due to corporate firewalls. Manually sideloading does require a few terminal/command prompt commands but is really very simple
For the sake of making this guide as simple as possible I’m going to assume the following
- You have ADB in your PATH
- You have no other Android device connected apart from a single Emulator instance
- Your emulator is up and running
- Your emulator has USB debugging enabled
- Your emulator has the “allow apps from unknown sources” option enabled
The first step is to make sure that your emulator can be seen by ADB. You can do this by opening either a Terminal Window on Mac or a Command Prompt on Windows and typing the following command:
This should display a list of devices containing only your emulator. If you see other entries disconnect the other devices. If you see no entries check to see if your emulator is still running, if it is see troubleshooting below.
Using either your terminal or command prompt change to the directory your target app is located and type the following command:
adb install <appname>.apk
The target app will now be uploaded and installed to the emulator.
If you get something like below, you will need to uninstall the app from the emulator first before sideloading
Troubleshooting – ADB doesn’t see my emulator
Sometimes ADB won’t pick up your emulator even though everything appears to be in place. The most sure way I’ve find to fix it is to follow the below steps
- In your terminal or command prompt type adb kill-server
- Go to your emulator and disable the USB debugging option, once that’s done enable it again
- Back in your terminal or command prompt type adb start-server
- When the adb server has started again type adb-devices and your emulator should now be seen in the list.