Mobile Automation With Appium, Robot Framework and Android SDK in Ubuntu Automation becomes an essential part of software testing. For the frequent changes/updates in any software it is necessary to have an fully automated process to test the software to ensure it’s functionalities are working properly.

I know that similar questions have been asked before, but my problem is new only after installing Android Studio 2.3, the latest version in March 2017. I have several years experience developing Android applications, and I have never encountered this problem before. After upgrading to version 2.3 of Android Studio, my emulator is no longer able to access the internet.

I even uninstalled/reinstalled Android Studio 2.3 from scratch and created a new emulator, and I am still getting the same error. This is not an app problem. I can't even access the internet from Chrome, and I wasn't having this problem last week. The message that I get says that the server DNS address could not be found -- DNS_PROBE_FINISHED_BAD_CONFIG. The only thing that has changed on my computer in the last week is the new version of Android plus possibly updates to Windows 10. And yes, my computer has access to the internet. Below is an image of my emulator when I try to use Chrome to search for 'Google'.

I have discovered an additional issue with Android Studio 2.3 that is not related to internet access but could somehow be related to the one above. With Android Studio open to a project and an emulator running, I can run the app on the emulator just fine. But if I open Android Device Monitor, it tells me that the emulator is offline.

Then, if I close Android Device Monitor and go back to Android Studio, it also tells me that the emulator is offline. I have to close and restart the emulator before Android Studio can find it again. This problem, like the one above, is repeatable. – Mar 11 '17 at 14:12 •. Another update. I installed Android Studio 2.3 on another, older/slower Windows 10 computer, and the problem still occurs. Also, at one point I thought that the problem might be related to a bad Microsoft WPD patch, but the older computer did not have the patch installed.

Plus, after several unsuccessful attempts, I was able to remove the bad patch from my main computer, and still no success in getting Chrome to work on an emulator. At this point I feel more certain that the problem lies with Android Studio 2.3. – Mar 12 '17 at 21:01 •. Notepad. I found a temporary solution on an old Stack Overflow thread at. Note that this thread talks about Android SDK 2.3, not Android Studio 2.3. The problem seems to be that the emulator can't find the DNS my computer is currently using, and the temporary workaround is to start the emulator from the command line and specify the DNS server.

Whatever problem occurred back then must have reappeared in the latest version of Android Studio. The temporary solution outlined below fixes the problem with the emulator accessing the internet. However, it does not fix the problem that occurs when trying to run Android Device Monitor. Doing so will still make the emulator go offline as described above. Note that there are two files named 'emulator.exe' in the sdk -- one under sdk tools and another under sdk emulator. Either might work below, but I use the one under sdk emulator.

The first step is to find where the SDK is located. Assuming a user name of 'jdoe' and a default installation of Android Studio on Windows, the SDK is most likely in C: Users jdoe AppData Local Android sdk The second step is to determine the name of the AVD (emulator) that you want to run. The command C: Users jdoe AppData Local Android sdk emulator emulator.exe -list-avds will show the names of your AVDs. How to format external hard drive. On my computer, it shows only one, Nexus_5X_API_25. To start the emulator from the command line with a specified DNS server, use something like the following: C: Users jdoe AppData Local Android sdk emulator emulator.exe -avd Nexus_5X_API_25 -dns-server 8.8.8.8 In this case, 8.8.8.8 is a Google public domain name server.