Having this issue since I upgraded the Android Tools to 21.1. When I start eclipse, even in a clean workspace, I get the error parseSdkContent failed and the details say:
com.android.sdklib.devices.DeviceManager.createInstance
(Ljava/lang/String;Lcom/android/utils/ILogger;)
Lcom/android/sdklib/devices/DeviceManager;
I have searched the internet and tried almost every solution but to no avail. When I go to Android preferences and try to set the path to the SDK , it says no target available. Is there anything else that I can try? I can't do any of my Android Development until it's fixed.
Step 1. Find the folder named: .android
This folder can be located in your Windows user directory, for example in Windows 7 or 8:
C:\Users\YOUR_WINDOWS_USERNAME\.android
Step 2. Delete this folder .android
Step 3. Restart Eclipse and your problem will be solved.
You DON'T have to delete ANYTHING
For me updating the DDMS from ADT plugin did the trick!
Before that, to save time I only updated ADT plugin, nothing else like Android DDMS, TraceView etc., so I ran into same issue.
After a couple of restarts and Google searches everyone was proposing different solutions. I updated my Android DDMS and restarted eclipse and it worked like a charm!
I didn't have to remove my workspace or update my .project file etc.
Ok I just deleted eclipse and reinstalled. Lost all of my settings etc. but it's all I could do. Something must have gotten corrupted in the upgrade of the ADT.
I had the same issue after installing 21.1 on a new machine. Solved it by deleting the default workspace I created during the first launch and then re-starting ADT as Administrator, recreating the workspace. After closing and re-running it as a normal user the problem disappeared.
Re-installing the new version of ADT (which at the time is ADT-23.0.3.zip(http://developer.android.com/sdk/installing/installing-adt.html)) helped me with the same problem you are described above. This message may be a little to late but hope this can also help others.
Uninstalling API 21 and installing API 19 worked for me.
In Eclipse, use the Check For Updates item in the Help menu to update the Eclipse-part of your Android tools (called ADT).
Try to go to your eclipse workspace and delete the .meta folder.
I was recently having the same problem and i figured it out that one must install/update other necessary software related to ADT.Suppose you are updating your ADT then you must also update DDMS with it.So,best option is to install the all software/plugin pack for the version you are updating.
When you uninstall the full thing and install it again,all of these related software get installed in same version so it always solves the problem.
According to me re installing should be final solution.
I got mine fixed by, before restarting your IDE, make your activity main layout as the current tab open, then restart your IDE. Hope it helps :)
This did it for me.
In Eclipse go to
Project Properties -> Java Compiler and set 'Compiler Compliance Level' to 1.7
For me I delete Android 5(API 21) installed software packages from SDK manager.
I am working on API 20 ( Android 4.4w.2). It only solved my problem completely.
Delete .android folder or others didnt help me out.
Deleting ".android" is temporarily fixing the problem with me as after sometime it begins to come again ..
Here is another cause and fix that might help .. This is happening because of existence of 2 versions of SDK in the same machine but in case you have only one version (probably it is 21) just download the SDK platform for API 20 (4.4W) as there is a problem in 21's "layoutlib.jar"). start applying the following:
Close Eclipse
Navigate to your sdk folder (something like C:\adt-bundle-windows-x86_64-20140321\sdk)
Go to platforms folder -> android-21 folder -> data folder and rename layoutlib.jar (for backup only)
Copy the same file (layoutlib.jar) from your android-20 folder to this folder "android-21"
Start Eclipse
maybe you have more than one android IDE installed, for example ,you installed android studio and adt+ eclipse all,just remove one can fix this problem
Related
Today, I clicked some update when I launch Android Stodio. I forgot what it is. Then, I run some code when there is a error
"8:34 PM IllegalArgumentException: Unable to locate adb"
Then, I google for few hours and still cannot solve my problem. And I found that there is no "adb.exe" under my platform-tools folder.
Can someone help?
my os is Window 10.
I have tried uninstall Android Studio and install it back. It doesn't help.
Edit 1: After I re-install the platform-tools, I get back the adb.exe.But, I run my program again, it does the "ADB initialization", my adb.exe file lose again.
I am writing the solution which worked for me:
go to SDK Platform Tools;
download SDK Platform-Tools for Windows;
extract zip file and copy to \AppData\Local\Android\sdk\platform-tools.
Had the same problem. Solution was that Avast deleted the adb.exe.
Try adding the SDK folder to your antivirus whitelist.
What worked for me (after having AS 2.x and AS 3.x installed and trying to get Canary 3.1 to work):
Sometimes during an update/trying to sideload a new version of Android Studio, the updater/patcher screws up. It might delete adb after saying it will stop and update it, it might be fastboot or aapt ... whatever.
What works for me is to delete the whole sdk/platform-tools folder, restart AS and get it to redownload the entire platform tools package.
Then start AS again and go to File->Invalidate caches/restart.
If you have been updating Java, you might also want to ensure your JAVA_HOME is correct and that your AS project has been set to the correct JDK (project settings).
Yep, looks like LOTS of folks (way too many, shame on you, Google) have come up with a missing 'adb.exe' symptom. (In my case, I claim that it never got installed at all, during my Windows-10 bundled installation of Android Studio,
version 3.1.2.)
Ok, here's my recommended solution (which I borrowed and modified slightly from
this question): Android Studio SDK installer hangs indefinitely at Unzipping 'platform-tools/systrace/NOTICE'
The second(?) answer is essentially correct..."Dx Arout" boldly and correctly recommends:
(1) Delete platform-tools from this location C:\Users\AppData\Local\Android\Sdk
and he/she's got the right idea, to then launch Android Studio and try to get it to complain and offer to fix the problem for you...says to:
(2) Then restart Android Studio. After gradle build finish it will ask for installation of missing tools. just click there. It should work fine.
Well, no, not quite. It didn't ask me anything, because I didn't get any
errors from current proj's build. So, I had to 'kick-it-in-the-*ss', by
launching Tools -> SDK Manager, choosing the middle tab ('SDK Tools'), and going to an already-installed entry named 'Android SDK Build-Tools 28-rc2' (your exact version entry may be somewhat different). So, click on its checkbox, choose 'Show package details' checkbox (down in lower-right corner). I lit up ALL the package variants, and forced it to install them all. That may have been overkill, but voila...once that completed, 'adb' DID get installed, as confirmed
when I launched a debug run. (Down in the 'logcat' tab's log-message window, the two RED headings, finally turned to black and debugging was finally USEABLE!
Cheers...
it's easy just go to your sdk location
like C:\Users\User\AppData\Local\Android\Sdk
there was to folder namely
platform-tools and platform-tools.backup.
open platfrm-tools.backup and copy the adb.exe and paste it to plaform-tools folder and now open the android studio again.studio will run smoothly and without any error
Thank you
I also faced the issue.
The avast antivirus had moved the file adb.exe to the virus chest and that was the cause of the issue. I have resolved it by restoring the adb.exe from the virus chest of avast.
Re-installing Android SDK Platform-Tools worked for me.
Go to: Android Studio >> Tools >> SDK Manager >> Appearance & Behavior >>
System Settings >> Android SDK >> SDK Tools
Uncheck Android SDK Platform-Tools >> apply
Check Android SDK Platform-Tools >> apply
The problem is solved. The issue I have is I upgraded the SDK platform-tools to 25.0.6. But My SDK Build-Tools is 25.0.3. (25.0.6 is not yet provided) I guess the version did not match which cause this problem.
I downgrade my SDK platform-tools to 25.0.3 and it is working as usual.
adb.exe won't appear if antivirus is installed and we need to whitelist this.
Anti virus block this because as it find .exe file so it will block it.
system deleted that file from platform tools u just make another copy of platform tools and whenever your system deleted your " adb.exe ". you can copy it to sdk/ platform .
this is a temporary solution i installed Quick Heal but its doesn't solve my problem
adb.exe is virus file for that its detected as malware
**
Solution 2 :
** Copy your SDK FOLDER in System folder where antivirus dont take action on it .
**
Solution 3:
1.Download new copy of Platform Tools
2.paste it into SDK
3.right click on adb.exe and go to security tab
4.disable access of deleting by user system USERGROUP
Solution 4
copy sdk in appdata/local it will solve your problem permanent .
Thank You
no adb found. I had to delete the virtual device from AVD manager create another. now virtual device connected succesfully
So I'm trying to create an AVD Simulator, and I keep getting the "No system images installed for this target" error when trying to create a 4.2.2 system even though the image is installed (See picture of SDK Manager).
My system is x64, does that make a difference?
After SDK Update I had the same problems with API Level 19 and
in my case restarting eclipse didn't solve it.
For some reason, in the sdk/system-images/android-19 directory, sub-folders with system images (armeabi-v7a and x86) were placed within "default" directory.
I just moved them into android-19 directory (if eclipse is running at the same time, you will have to restart it).
You just need to restart the tools. I have seen this bug before. The appropriate installed images will show up after the restart.
You can also try to refresh within the 'Packages' menu, but the easiest thing, is to restart the tools.
Goto sdk\system-images and open the folder of the current API you are using (eg.android-19 folder in your case).
Now you'll find a folder named 'default', open it and you'll see the folder named 'armeabi-v7a' or which ever system image you've installed.
Now move the folder 'armeabi-v7a' to the directory sdk\system-images...i.e simply out of the 'default' folder.
That's it.
I had the same problem and this method worked for me. :D
I restart eclipse.it worked out for me,issue is resolved.
I just had this same issue. My problem was solved by killing eclipse (Command + Q) because I'm a Mac user. So, if you're under other operative system be sure to kill the Eclipse's process and relaunch it.
Lots of potentially useful answers here, but none of them were worked for me.
On my Mac, I have both Android Studio and Visual Studio installed. One would hope that they would automatically look for an Android SDK in the same place, but no, not necessarily.
In Android Studio, go to Tools -> Android -> SDK Manager. In the window that pops up, make a note of the Android SDK Location. It should be something like
/Users/[user]/Library/Android/sdk
Next, in Visual Studio, go to Tools -> SDK Manager. In the window that pops up, the path that should be selected on the left is Projects -> SDK Location -> Android. On the right, click the Locations tab. For me, the Android SDK Location path was set to something like
/Users/[user]/Library/Developer/Xamarin/android-sdk-macosx
I changed this to the path that Android Studio was using, and that fixed the problem for me.
Very simple. I restarted Eclipse, reloaded my project and when creating a new emulator, the problem is gone
Found this thread when I did a search on Google for the same error.
So I just wanted to add that if anyone comes across this thread but you are using Android Studio. You only have to restart the Android Studio. I did and now I can see what I installed.
Make sure you have rights to all the files in the android-sdk-linux directory using:
sudo chown $USER -R ./android-sdk-linux
This seems like a trivial task, but I can't find an option to cleanly de-install the ADT from my Eclipse installation.
Of course, I could just delete the folder of the SDK, but this just throws errors when starting up Eclipse the next time. The reason I'm asking is because my old ADT keeps throwing a wierd error (Failed to fetch URL https://dl-ssl.google.com/android/repository/addons_list.xml, reason: File not found) and I need a complete, fresh re-install.
Important:
under
Help -> about eclipse sdk -> installation details
the uninstall button for all android plugins is greyed out
The only way to remove the ADT plugin from Eclipse is to go to Help > About Eclipse/About ADT > Installation Details.
Select a plug-in you want to uninstall, then click Uninstall... button at the bottom.
If you cannot remove ADT from this location, then your best option is probably to start fresh with a clean Eclipse install.
I found a solution by myself after doing some research:
Go to Eclipse home folder.
Search for 'android' => In Windows 7 you can use search bar.
Delete all the file related to android, which is shown in the results.
Restart Eclipse.
Install the ADT plugin again and Restart plugin.
Now everything works fine.
I had the issue where after updating the SDK it would only update to version 20 and kept telling me that ANDROID 4.1 (API16) was available and only part of ANDROID 4.2 (API17) was available and there was no update to version 21.
After restarting several times and digging I found (was not obvious to me) going to the SDK Manager and going to FILE -> RELOAD solved the problem. Immediately the other uninstalled parts of API17 were there and I was able to update the SDK. Once updated to 4.2 then I could re-update to version 21 and voila.
Good luck!
David
If running on windows vista or later,
remember to run eclipse under a user with proper file permissions.
try to use the 'Run as Administrator' option.
i got the same problem after clicking update plugins,
i tried all the suggestions above and failed , the only thing that worked for my is reinstalling android studio..
I am going nuts.I update to the Android SDK in Eclipse, Eclipse can't find the SDK. There is a text not that saids the the file has been moved to /platform-tools, however the file ADB.exe is nowhere to be found in any of my folders. The SDK Manager works find but for some reason Eclipse will not find the file its looking for. I have looked everywhere for the answer. It work find for about 4 months until I upgraded. I also now using a real device a Droid X2. But I don't believe this is the issue. I can't find the ADB.exe file. Help been working on this for about 2 days
adb.exe was relocated from {ANDROID_SDK_FOLDER}/tools to {ANDROID_SDK_FOLDER}/platform-tools: find your SDK folder and look inside it for the platform-tools folder.
EDIT: in Eclipse, if you open the Preferences dialog (Window->Preferences) and select the Android option on the left it will show you what Eclipse THINKS is your Android SDK folder. If you moved the SDK folder you should update the path to match the new location of the SDK folder, and then (a restart might be necessary) Eclipse should work fine with the Android tools.
EDIT: well, I can't tell if your ADT isn't properly installed or if the SDK location is broken, so lets try and brute force set the SDK location. Create a text file on your desktop called "adt.pref", and then place only this line in it:
/instance/com.android.ide.eclipse.adt/com.android.ide.eclipse.adt.sdk=C\:\\Program Files\\Android\\android-sdk
then in Eclipse select File->Import then select General->Preferences and then pick that file. This should force the ADT location to match what that is. Restart Eclipse and see if that improves things.
I had the same problem and solved it by running the android sdk-manager (you can do that without running eclipse, using the start menu shortcut) and installing the Android SDK Platform-Tools through it (select the square and click install packages...).
Download the SDK here.
Once that's done, I would just follow the Google installation instructions again from the beginning. Perhaps you're missing something fairly simple?
Installation instructions.
I got the same problem. In my case it was caused by an upgrade on the Java JDK. I was using 1.6 and upgraded to 1.7.
Just manually add the new JDK to Eclipse.
Right click on your project JRE System Library. Select installed JRE, and then find it on your computer.
I had the same problem, and when I looked inside the platform-tools folder, it was empty.
After searching for downloading the contect of this folder, I found the below link.
http://venomvendor.blogspot.com/2012/06/android-adt-20-updated-download-offline.html
But it also could not help me.
At last I found that it's related to my internet connection.
I'm using Windows 7 and installed the 64 bit version of Eclipse 3.5.2. I then installed the Android ADT plugin, but when I try to configure it in the Windows > Preferences dialog, the Android Plugin doesn't show up in the left pane. Instead I see DDMS. This prevents me from specifying the location of the Android SDK (unless there is another way) to give me the appropriate templates and such.
Someone posted a fix to this that includes setting the permissions of Eclipse, but that didn't work for me. I tried installing the Android Plugin from both online installation (thru the URL install) and the offline Archive method.
If you're running Windows Vista or 7, make sure you right-click Eclipse and RUN AS ADMINISTRATOR. I literally spent six hours figuring this out, and this was what fixed it.
Dear people from the future:
I had roughly the same problem in linux, except that i didn't see anything at all but vanilla eclipse after installing. by combining both previous answers i got it to work:
start eclipse with sudo eclipse -clean, install the plugins and restart eclipse. the plugins showed up including the welcome screen that's supposed to be there.
after that it should work when running as regular user as well.
works for both the android sdk and the gwt sdk. (and probably other eclipse plugins)
Remove the plugin, then restart as follows:
eclipse -clean
Now try reinstalling the ADT from the online installation
For users having similar problem and not luck with other solutions:
I have windows XP but had same problem. I realized that I had JDK5/bin folder in my PATH environment variable (though my JDK_HOME was pointing to JDK6), as soon as I modified the PATH to replace bin of JDK5 with JDK6, the Android buttons on eclipse (after restart with -clean) along with Android option in Preferences & New Project showed up. (Weird eh!)
Also, consider to install the bundle android installation having eclipse with pre-configured Android SDK if a new eclipse installation doesn't matter to you
http://developer.android.com/sdk/installing/bundle.html
The above answers do not confront the heart of the problem. There is a feature in Windows 7 that prevents downloaded files from direct access of local files. All of the state is perfectly maintained in the Eclipse workspace instance. The problem is easily resolved by doing the following:
Find the "Eclipse" executable
Right-click on it.
Click "Properties".
Select the "General" tab.
Look for -> Security: "This file came from another computer and might be blocked..."
Click Unblock.
This is a much better solution than uninstalling and reinstalling the ADT or Eclipse which can be a pain.