Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Running Program with Emulator, "Local SDK Path not set!"

When I run my program with the emulator on Android Studio I get an error as follows

Local SDK Path Not Set

When i checked this in my project structure my SDK path is

C:\Android\sdk 

and this is the same in my SDK Manager. I'm new to Android Studio and am curious of why my emulator loads, but does not run my program.Any help in this regard will be appreciated

like image 850
B.Quinn Avatar asked Sep 29 '16 03:09

B.Quinn


People also ask

How do I fix sdk location not found?

Close the current project and you'll see a pop-up with a dialog which will then proceed to Configure option. Configure -> Project Defaults -> Project Structure -> SDKs on left column -> Android SDK Home Path -> give the exact path as you did on local. properties and select Valid Target.

How do I change the sdk path?

To set the Android SDK location, enter the full path of the Android SDK directory into the Android SDK Location box. You can navigate to the Android SDK location in File Explorer, copy the path from the address bar, and paste this path into the Android SDK Location box.

Where is my sdk path?

Navigate to the File > Settings option you will get to see below dialog screen. Inside that screen. Click on Appearance and Behavior option > System Settings options and then click on the Android SDK option to get to see the below screen. Inside this screen, you will get to see your SDK path.


2 Answers

In the menu Run > Edit Configurations if you have the deployment target as "Emulator" with no preferred device selected you may run into this issue. Instead, choose deployment target as "Open Select Deployment Target Dialog". This will let you select from any installed emulator or a device connected by USB. Make sure to hit "Apply" before closing the Edit Configurations menu.

Edit Configurations with Emulator but no Emulator

Edit Configurations with Open Select Deployment Target Dialog

like image 137
timclancy Avatar answered Oct 12 '22 23:10

timclancy


I ran in to the same problem after synchronizing gradle. All I had to do was turn the emulator off and on again to fix the problem.

like image 39
WARdd Avatar answered Oct 13 '22 01:10

WARdd