I am using the following:
Android Studio 1.4
Windows 7 x64 PC
I installed Android Studio in the D: drive.
Now whenever I click the run option, it throws the errors,
no emulator binary found
and
mksdcard.exe missing from sdk tools folder
I cant even create avd. It is just showing saving avd .
I removed and installed haxxm once again although it still wont work. Please help me..
Quick tip that fixed error in my case:
Move everything from "emulator/emulator" to just "emulator" level in sdk directory
OR
Reinstall emulator via GUI
TL;DR
My error in "idea.log" was:
vdmanager.AvdManagerConnection - 'mksdcard' is missing from the SDK tools folder
My environment:
macOS Big Sur, Android Studio 4.1
How to find "idea.log": Help | Show Log in Finder
Solution that worked for me:
Note down "Android SDK Location" (see Preferences | Appearance & Behavior | System Settings | Android SDK)
Open the path from #1 in Finder or other file manager
Make sure "emulator" folder is there
In my case the required file was located 1 level lower, namely at "emulator/emulator" subfolder of sdk, not just "emulator"
Move everything from second level of "emulator/emulator" to first "emulator"
NB: I would have preferred symlink'ing the items, but the "emulator" directory contains an executable named "emulator" so there was a conflict of already existing name. Besides, reinstalling via GUI (see next solution below) creates just 1st level of "emulator" which proofs that moving is OK.
OR
Re-install emulator:
Preferences | Appearance & Behavior | System Settings | Android SDK | SDK Tools | Android Emulator
Clean checkbox, "Apply" (this will remove emulator)
Mark checkbox, "Apply" (install emulator anew)
The issue can still happen in 2021. I'm not sure about the reason it took place six years ago. I had multiple errors related to the fact that Android Studio 4.1 downloads files to one location but expects them to be within folder at an upper level. This also concerns settings folder that moved from "/Users/sign-in_name/Library/Application Support/AndroidStudio4.0" to "/Users/sign-in_name/Library/Application Support/Google/AndroidStudio4.1"
Related
In short: I am unable to run my app in the iPhone Simulator. There is no "Play button" (the triangle), only a Debugger button (hammer):
As you can see above I have "Generic Simulator". When I click on it, there is no list of various iPhones/iPads to choose from:
If I choose Android, I am able to run the app:
I have XCode installed. I ran XCode once.
I also installed the Command Line tools.
I created a new Xamarin Forms App:
Here are my iOS build options:
I am able to run the Simulator separately:
Creating an App in XCode and running in the Simulator works:
info.plist:
Prefrences -> SDK Locations -> Apple
Build -> Configurations:
Here is the kicker though. If I run a Xamarin App on my Windows machine using the iPhone Simulator on the Mac, it works!
What do I need to do so I can run my app inside the Simulator vis Visual Studio for Mac?
Few options you can worth to check. #WorldOfBasti suggested options plus following.
Configuration
Right click on the solution -> options -> Configurations -> Configuration manager -> ProjectName.iOS with Debug|iPhoneSimulator should be checked or if configuration "ProjectName.iOS with Debug|iPhoneSimulator" is not available then add this from General tab
Apple SDK path
Check Apple SDK path is set properly (Preference -> SDK Location -> Apple). It should have green tick mark with Xcode version and SDK path location.
Minimum system version (Deployment Target)
Change Deployment Target to minimum version (ie, lower than your simulator version)
Switch debug <-> release
Today I have also faced same issue which you are facing. I have switched debug to release, iOS to Android. Then reverted back to iOS and debug from the top device selection status bar. Then Simulator option was appearing. So, might be UI updated issue in Visual studio for mac. Please give a try.
I assume that you tried the basics things like restarting your Mac, etc. So here are a few things, that might solve your problem:
Check your build configurations, here is a good video
Close VS for Mac, start Xcode and create a test project which you run on a simulator. If it works try again in VS for Mac
Close VS for Mac, goto Xcode -> Preferences -> Accounts and download the manual profiles of your developer account. Try again in VS for Mac
Clean your project: In VS for Mac, goto Build -> Clean All. Then Close VS for Mac, goto your project folder and delete in "yourprojectname" and "yourprojectname".iOS all bin and obj folders. Try again
If all of this doesn't work, I would try to reinstall it (if you have any important projects, make a backup):
Uninstall VS for Mac and Xcode
Install Xcode again from the App Store
Install Visual Studio for Mac
Hopefully it works..
Looking at the Visual Studio for Mac logs, specifically the IDE log, I found this line ... 'The target name of simulated device could not be added because it's already cached'.
You are welcome to read through all of this ... but you may just want to go down to the Addendum 2 (final?) and see if that works for you ... it ends up being simpler and quicker than anything else I have found.
So, at first, I started clearing the cache with a 'xcrun simctl erase all' command from Terminal, and when I started Visual Studio for Mac I could run a Xamarin App, but launching the simulator took quite a bit of time.
So hare's something I found works that you might want to try ...
Close iOS Simulator on Mac (if any).
Close ALL copies of Visual Studio that are connected to the Mac ... either on the Mac itself or on another computer connected to the Mac (if any).
Start Visual Studio for Mac.
If you can't run a Xamarin App, Close Visual Studio for Mac.
Launch the Simulator manually (I have it in the Dock, so I just click it) ... wait for it to fully startup.
Now close the Simulator (from the Simulator menu).
Now restart Visual Studio for Mac.
If you still can't see the simulator devices to run on ... try the above steps one more time (this time you should only have to close Visual Studio for Mac followed by manually starting the Simulator, waiting for it to start, and then quitting the Simulator and finally restarting Visual Studio for Mac).
It still isn't great, but this has (so far) always worked for me. And the Simulator starts up substantially quicker then if I did a 'xcrun simctl erase all' command from Terminal.
Addendum: Most of the time the above works. But occasionally I still have to clear the cache from the Terminal with 'xcrun simctl erase all' command.
Also: I have also found (although maybe it's just my imagination) that clearing out the Visual Studio for Mac temporary .binlog files that are written in the 'T' folder will sometimes fix the problem (if you look at an IDE log from Visual Studio for Mac; right after the 'The target name of simulated device could not be added because it's already cached' message, you should see some .tmp files being created. The directory where they were created is the 'T' folder I'm talking about). I sometimes delete the tmp*.binlog and tmp*.tmp as a last ditch effort before using the 'xcrun simctl erase all' command to try to get back to where Visual Studio for Mac will see the iOS Simulator Devices.
Finally: This is really starting to feel like a bug in Visual Studio for Mac startup (or possibly during a iOS project load). The reason I say that is I can ALWAYS see the iOS Device list from Visual Studio for Windows (as long as I can connect to the Mac). In addition, I can leave Visual Studio for Mac running (even hidden) and test an app on the iOS Simulator from Windows, then, leaving the iOS Simulator Running on the Mac, run an App on Visual Studio for Mac. If there really were a 'caching issue' with the Simulator it seems to me I should have problems running anything on the Mac after using the iOS Simulator from Windows, but it always works. For now, I'm working on a single Xamarin Project on the Mac (and I don't use the Mac for anything else), So I just let Visual Studio for Mac 'open at login' (Dock setting) and automatically 'load previous solution on startup' (Visual Studio for Mac setting), hide Visual Studio for Mac (Dock Setting) and if I need it, Visual Studio for Mac is already loaded and able to see iOS Devices to run Apps on with a quick click on the Dock Icon.
Addendum 2 (final?): I have now found that if I just close a solution that I have open that shows 'Generic Simulator' and re-open it without exiting Visual Studio for Mac (sometimes I have to do it multiple times ... I think I've counted up to 5 times before it finally worked), it will start showing the device list and I can run the iOS app in the Simulator. I don't even have to close the Simulator if it's already running, which saves a bunch of time.
It still feels like a bug to me, I don't see why I would have to close/open a solution multiple times to get the iOS devices listed and be able to run an iOS app. What really gets me is if I reboot the Mac, don't open the Simulator and start Visual Studio for Mac, then open a solution, I still have to go through the close/re-open solution steps... sometimes more than once. The simulator is not set to auto start or anything like that. But, at least, it's getting simpler, and takes less time, to get to a point where I can run an iOS app.
I have pulled an Appcelerator project from our developer group and unable to publish or run the project on a local Android device.
When trying to publish the below error screen immediately pops up.
Android SDK version 4.1.2 not found.
I have checked both in the Appcelerator platform settings and Android Studio config and have the SDK installed.The install SDK screen in Appcelerator Tried uninstalling/reinstalling Appcli and the SDK to no avail.
After a few days of searching all the appecelerator files in my project. I finally found the fix for my problem (for anyone googling this).
There's a hidden file in the root of the Appcli project called .settings
Inside of settings there's a package called com.appcelerator.titanium.android.core.prefs
There is an android/sdk_version=4.1.2 that was causing all my issues. Hope that helps someone.
Most likely, your issue seems to be with unsupported Android SDK version as per Ti SDK you are using.
So before doing anything, try to grab what this page says to know all about software compatibilities: Titanium Comptability Matrix
It says that minimum Android version as of latest Ti SDK 6.x.x is API 16.
Now, follow these steps carefully to get a fresh start on your system.
First of all, download Android latest SDK from here: Android SDK
Unzip it & put it in at some simple path like in /Users/username/android-sdk
Download Appcelerator Studio (AS) & install it. It will download all pre-requisites like Java, Python
Open Appcelerator Studio & go to Preferences->Studio->Platforms->Android. Select the path of android sdk you unzipped in step 2.
After all these steps, you can open Android SDK Manager (see screenshot where it is) & install necessary SDK, Tools, etc.
Note: I do not suggest to download SDKs via AS as I have faced path issues in beginning.
Even if these steps do not help you, then provide us the log output after running this command on terminal: appc info
If terminal says this command is not found, then you need to go through the AS installation properly.
I had the same issue. Simply deleting all " Android Play Store Distribution" configurations solved my problem.
Apparently this is not a problem and someone proposed a solution that apparently works on Windows, this issue still exists on Mac.
Although the SDK installed by Android Studio on its default path (/Users/user/Library/Android) exists, Xamarin installer still wants to download a "private copy of android sdk":
Does anybody know a workaround?
I had this same issue. You can either add the path to the downloaded SDK by clicking the + button, or create folders in the default Xamarin location and then copy the sdk there.
Even though I tried this, a new Android SDK had just been released. The Xamarin installer was intent on downloading the latest version though, and I eventually ended up leaving it to complete.
I was able to change the Android SDK Location in Xamarin Studio to use what was already installed on my mac:
Xamarin Studio top right menu
Xamarin Studio Community
Preferences
SDK Locations
Android
Android SDK Location : Browse and choose the location of your android install; it's usually at the following location on a mac -> user/Library/Android/sdk
I am 100% new to Xamarin seem to have done something wrong in Visual Studio 2015. I am just trying to view my Main.axml file however the designer is giving me the following error:
A valid Android SDK could not be found. An existing SDK with platform tool and at least one platform needs to be registered with the IDE.
Do I need to do soemthing specific to fix this?
As you can see I am targeting Android 4.1 API 16.
Another weird issue is that the Android SDK Manager is disabled is this normal?
visual studio -> tools ->options:
To launch Android SDK Manager I have to launch Android studio and click on Android SDK Manager :
I had same issue with my sdk on visual studio. I could not open sdk manager from visual studio and xamarin designer could not open even though i pointed to an sdk location. however, other things worked correctly. Updating sdk from android studio and upgrading jdk to 1.8.0_102. solved my problem.
While the Xamarin is updating, that error can see.
Solved is found the tools zip file:
C:\Users\User Name\AppData\Local\Android\android-sdk\temp\tools_r25.2.4-windows (or your active last tools, doesnt matter. for ex. tools_r23.0.1)
-> Open that zip and unzip in "tools" folder.
-> Cut that folder and, paste parent folder (C:\Users\User Name\AppData\Local\Android\android-sdk)
Delete files from this path:
C:\Users\ ++ Your Windows Account Here ++ \AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache\
All the solutions posted here on stack overflow dont seem to suit my situation. I am using visual studio. How do I fix this error while not ruining the setup for monotouch? Monotouch docs say explicity that I should not at all start the image but monodroid will do it.
I am using mono for the android with visual studio. and soon will be using monotouch for IPhone
When you get the Invalid command-line option: Files, you should do the following (just fixed it on my machine):
Uninstall the Android SDK (if you have downloaded images, make a backup copy of the installation folder first)
Install the Android SDK again, but make sure you install it to a path that does not contain spaces. C:\Android will work fine.
After installation has finished, copy the backup copy over the newly installed version. Then you will keep your downloaded system images.
This apparently occurs because the Android SDK has a bug in the latest version when it comes to folders with spaces in them. Weird.