Why does Genymotion install successfully but fail to connect?

Question

Why does Genymotion install successfully but fail to connect?

Topic: Account & API Access

Q&A ID: 1217

Source Confidence: 86% (based on semantic similarity to source pages)

Accepted Answer

“It's installed but won't connect.”

If you’re using Genymotion Desktop, ADB is supposed to connect automatically to the first running local virtual device. If it still does not, set the Android proxy again and make sure the Burp certificate is installed correctly.

For Genymotion Desktop, the proxy command is adb shell settings put global http_proxy <burp_proxy_ip>:<burp_listening_port> and you can clear it with adb shell settings put global http_proxy :0 (How to connect a virtual device to a proxy?).
If you need HTTPS interception, install the certificate as a user CA or system CA depending on the Android version, then reboot the device (How to connect Burp Suite to Genymotion).
For Genymotion SaaS, you must connect the running instance to ADB with gmsaas instances adbconnect <instance_uuid> before using ADB commands (How to connect a virtual device to ADB in Genymotion SaaS?).

What Genymotion product and Android version are you using?