I am trying to install the ADT plugin for Eclipse. However, after I have went to "Install New Software..." and entered the plugin location https://dl-ssl.google.com/android/eclipse/, "Pending..." is displayed. It does not change to "Developer Tools" no matter how long I wait. (I have also tried "http://dl-ssl.google.com/android/eclipse/)
To get around this I tried downloading the current ADT Plugin zip file, but this does not work either. "Developer Tools" appears, but when I click "Next" it does not move past "Calculating requirements and dependencies."
Please provide a solution to the problem of either approach. Thanks.
I had the same problem. It started working when I unchecked the box labeled
"Contact all update sites during install to find required software".
Goto Preferences->Network Connections and set the correct option (native/direct as per your proxy settings on your network) restart eclipse and try again. [Switching to direct worked for me at home, however in office i had to configure it to native..] (Proxy settings require restart of eclipse IDE on some machines to take effect)
Ensure that your eclipse has all android toolkit dependencies (wst/emf...) installed (http://developer.android.com/resources/faq/troubleshooting.html#installeclipsecomponents)
Update
The logged error you provided leads to Install from updatesite hangs under Java 7 and in turn Eclipse Bug 362741 - downloads from update sites hang - (3.7.1 Indigo SR1 windows), see comment 6 specifically (you already applied comment 7).
Please note that while this seems to be a JDK 7 problem at first sight, the linked Java Bug 7077696 - java.net.Socket closes when "PASV" is sent on an authenticated FTP connection classifies the issue as a REGRESSION. Last worked in version 6u26, while you are using 6u30 already. Accordingly, the issue is reported to be fixable by switching to Java 6 elsewhere (implying an earlier version), see e.g. Cannot do any software installs using jdk1.7.0_01 (which uses 6u22):
However, everything works right if I then change the eclipse.ini to
change the vm to JDK 1.6:
-vm C:\Java\jdk1.6.0_22\bin\javaw.exe
Oracle's Evaluation concludes, that This does not appear to be a JDK bug, rather it's just the Windows firewall recognizing and blocking the ftp protocol.:
The only
difference between JDK7 and older releases is that the JDK is using
IPv6 sockets when IPv6 is enabled and so IPv4-mapped IPv6 addresses
are used. it may be that Windows or the firewall is not configured to
allow IPv6 sockets. [...]
Accordingly, they list a Workaround as well:
Run with -Djava.net.preferIPv4Stack=true
add a firewall exception for the Java binary.
run with -Djava.net.preferIPv4Stack=true (which disables IPv6 and uses AF_INET sockets exclusively)
or disable stateful FTP inspection in the firewall (registry setting or netsh command)
The firewall adjustment seems to be a confirmed workaround as per comment #4 in Socket Exception only in Java 7 (though simply turning it off like there should be handled with care of course).
Good luck!
Presumably you are already aware of Robamaton's answer to Eclipse, Android Plug-in, Install New Software just says “pending” (there are many ADT related questions and strangely it didn't show up immediately in a respective search)? It basically comes down to Codejammer's hint towards Preferences->Network Connections (+1), though with an explanation why it might still fail on your network regardless, see the comments:
Oh, I read that it doesn't respond to general requests from browsers.
In any case, network admin confirms it's making a socks connection,
but then doing nothing further.
and
Ok, further to previous comment, it's probably trying to connect via.
socks 5 - but our network only has socks 4. Admin is going to run the
5 version to see if it then works.
Workaround
Regardless of whether the socks 4 vs. socks 5 proxy settings are actually the problem, a potential workaround might be to install Eclipse and ADT on a different system (ideally on a different network), and copy the resulting folder to yours thereafter (after all, an Eclipse installation is simply a collection of files).
When doing so, please ensure to match 32- vs. 64-bit regarding both the JDK and Eclipse between the source and the target system, because a mismatch would yield other problems (see e.g. my answer to Failed to load the JNI shared library on starting Eclipse).
What versions of eclipse are you using?
In Helios I was able to install the plugin by going to Help -> Eclipse MarketPlace -> Yoxos MarketPlace (Second Icon at the bottom) and search for ADT and install.
If you were unable to get network update working, please try downloading the ADT zip package and installing locally as the download page says.
http://developer.android.com/sdk/eclipse-adt.html
I find these google sites very difficult to connect with from certain networks, but not from others.
Here in Germany, I had terrible trouble going through Alice, but none going through Deutsche Telekom.
Sometimes I could reach the dl-ssl host from Alice, but in some later operation it would hang then time out.
A day or so later, I might be able to make a connection again. Some people say they had luck going through a proxy, or by changing "http" to "https". I also saw this.
Here's what I think is going on.
First, Eclipse is miserably buggy, and handles unexpected situations very badly (for example, catching all exceptions, but failing to provide the exception's message!!), particularly when it comes to unresponsive links. It reminds me of the stock story of the mentally disturbed psychiatrist.
It looks as though the google server is badly configured, possibly as a naive protection mechanism meant to repel denial-of-service attacks: it only handles a few connection requests within a certain time frame from hosts certain networks, and if it gets too many requests, it locks out connections with the host for a long time.
Unfortunately, a single Eclipse update might require many connections in rapid succession; somebody unsure of how to configure Eclipse the first time will likely trip the Google booby-trap.
In my case, I was able to download what I needed by carefully choosing a subset of the available software, being very patient, and if I got locked out, just waiting a day until it let me in again.
Cheers!
I had the same problem and it was driving me nuts. I kept trying for a couple of hours--getting the same error message--and at once it worked! So if I were you I'd just leave it for a bit and come back in a couple of hours and try again. There are several other suggested solutions online that I found, but neither of those seemed to make a difference.
I've faced with the same problem before. In my case this was a problem that I was working under the proxy. I think you also work behind a proxy.
I've solved this problem in the following way. Find the SDKManager.exe and run it. In this program find proxy configuration and fill it there. Then from this program try to update your SDK (maybe this will require you to restart this program).
I do not know why but Eclipse proxy configuration is not working in case of Android ADT.
P.S. You have to use JDK 6 (or 5), not JDK 7!!!
Use Following link to update ADT Pligins.
https://dl-ssl.google.com/android/eclipse/site.xml
The only answer I found out when I got this problem was to download the latest 'Eclipse Indigo for Java', updating the ADT and android SDK.
After few hours, everything was normal.
Turning off IPv6 worked for me.
In my case I use proxy setting, and I follow the instruction of this post. But just one small modification: the SOCKETS setting should be clear and empty as suggested by here
Related
Here is the error I'm getting when trying to archive my app for deployment.
This error doesn't show up at any other time. The project builds and runs on emulators and devices without issue. This error has zero context or direction as to where to look to fix it. It also just randomly showed up out of nowhere, last time I built/archived (with zero functional changes) this error did not happen.
Main difference between this archival and the previous one is a newer version of VS 2017. Don't remember exactly the version from before, but am currently on 15.9.4 (stable).
Looking around on the interwebs, I've found that this error seems to have something to do with ObservableCollection's, which there are probably 10-ish in my app. Not really sure what to do here, because this has never been an issue previously, and I'm coming up on a deadline and with the structure of the app, am not in a good position to start making functional changes.
EDIT
I have also cleaned and rebuilt my solution, as well as deleting all bin/obj folders in my xamarin projects. Even tried deleting the .vs folder which can sometimes help. But still no go.
Going to try updating VS to 15.9.5 and see if maybe it was fixed in a release.
EDIT 2
Updating VS 2017 to 15.9.5 made no difference.
EDIT 3
I had my coworker try archiving the exact same project on his machine (running VS 2017: 5.9.3, and it archived fine for him. So far that's the only difference we've been able to find between our environments.
I saw the same problem using VS2017 15.9.9. Even the same code that could be archived a week ago threw the above mentioned error. It seems related to local data in the solution. A "clear" build was not sufficient. However manual deletion of the local obj and bin folders followed by archiving (build is done implicitly) solved the problem for me.
For my part closing Visual studio and deleting the .vs hidden folder did it.
It's actually a fix for many issues using Xamarin.
I had this other issue where I couldn't archive because the build process would just hang and never end. Deleting the .vs folder did it too.
https://github.com/xamarin/xamarin-android/issues/1760
Just go to project property then go to Android options-> Select Advanced then increase the Java Max heap size to 2G/3G -> it's working for me.
Leon Lu's suggestion worked. I don't particularly like it, as it took forever and repairing basically restores you to a base install (no extensions or personalizations). Took about 1.2 hours to complete, but once done I was able to again archive my android application. I guess something went wrong in vs at some point, perhaps during an update. There's no way to tell.
I tried ALL of the ideas above, but had no consistent reliable luck with any of them.
I found that Microsoft has had the problem reported to them (see link below). After a ton of time burn on this, I posted at the link below one way that I've been able to get around this archive-build issue.
Like the other fixes, it's not exactly logical, and nothing that you would think would work, but I've found the process to be repeatable, which is golden for me with tight timelines and having no time for this.
MS Visual Studio Developer Community Problem 507708
Posted on a Saturday morning, a sign of really needing to get around this urgently. I hope it helps you too.
I'm having this problem when I debug my app. It blocks at this line and I don't know what is causing it. I could not find any answer or anyone that had the same problem. I have no clue what part of the code could cause this to happen. Do you have any ideas or have experience with this?
I'm using
Android Studio 3.1,
JRE 1.8.0,
JVM: OpenJDK 64-bit
Waiting for a blocking GC ProfileSaver message appears for me when I have set too many break points.
This link will help if you are looking to manage your break points.How to effectively remove all breakpoints in Android Studio
I solved this by wiping out all user data from the emulator and reloaded the app. You may use this step if you are absolutely sure about loosing user data.
Go to Android Studio, then in Tools menu click on AVD Manager and select your virtual device and click on wipe data
As may be seen in the attached picture
It happens to me too. But not only in debug, but also in real. As you say, one of 10-15 times when I sign in. I think the problem is derived from http connection problems. This has happened whenever I load the initial data.
I faced the same problem just now, I tried another device and the application worked usually, then I knew that the problem is in the device I used not in the code itself. To fix that, I wiped the device data and it works again.
Good day guys
I have this kind of problem from my Eclipes Juno
I can't create a new android project because of this one
and i found several topics about this problem
but almost of the answers was pointing into two solutions
"Uninstall the support library from the Android SDK manager"
"have an internet connection and update online"
and i have two problems too...
first, i don't have internet connection in our home
Second, "i don't have it" (Support Library)
This is my android SDK
as you can see I have no Support Library so notting to uninstall
maybe you'll be confused "where did i get that platforms if as i said i have no internet connection in our home"
well i've manually downloaded all of it and manually extracted to my "plaform" directory....
i have encountered some errors before like this one
and luckly i was able to solve it using just manual downloading and extracting (a little workarounds)
but this one seems to be one of the hardest to me for now...
I keep browsing the web for finding such a "support library.zip" so that all i have to do is extract that one to its respective directory
and a step by step to where do i extract it... but sadly i found nothing...
i im thinking of some posible solutions
and maybe i need a help of a person who has a good running Eclipse Juno
make a request like " can you zip your support library folder from your SDK and upload it here"
and a simple "path" to what directory do i have to extract it.
whatever it maybe...
ill just trying every single workarounds just to solve it "offline"
i know online solution is less hassle and just a little clicks and problem solved,
but did you know how it happened?
do you know what eclipse or SDK did to solve that?
that's the reason why i want it offline just for me to understand every bit of it...
i want to solve it Offline...
Thank you in advance.....
you can go to download ADT-20.0.0.zip ,Install it and then restart Eclipse.
because Google is 2.2 and the earlier version to official library, support many 3.0 and higher version of the function, in the new construction time, the default will give you add libs folders and android - support - v4. Jar。
I also can be directly sent to you ADT-20.0.0.zip。please tell me your E-mail！
few days ago, when I was debugging an Android project under eclipse I've found some great functionality: "All instances..." and "Instance count". I wanted to share my findings with rest of my colleagues, but none of them had this functionality in their eclipse install (we all use eclipse 3.7).
What's even more weird now I'm also missing this functionality.
As far as I can tell this functionality is build within eclipse from version 3.3 and available to projects using Java 1.6 and above as mentioned here and here (we're using 1.6).
See bottom of this link to see what functionality I'm talking about. It even has it's own shortcut in options (ctrl+shift+n) so I think there must be a way to use it again.
I was looking for it while debugging and while the debugger was in "stopped" state.
Anyone can help me put eclipse in right view/perspective/state to see this functionality again?
EDIT
Here is the documentation entry from eclipse help page: link
Thanks for any suggestions,
kajman
After some more digging I came to following conclusion:
DalvikVM does not support "instance retrieval".
On eclipse help page mentioned in EDIT section it written:
This command is only available if the Java virtual machine you are currently using supports instance retrieval.
Maybe there is an option to enable this option in DalvikVM, but I doubt it unfortunately.
Also when debugging on phone "Drop to frame" functionality is missing.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
android SDK and AVD manager getting stuck
This is not the same as some of the other SDK Manager errors people have already posted on SO. Others have posted about permissions problems, and occasionally someone runs into some kind of database error.
In my case, the progress bar will just stop updating, and the whole thing will just sit there indefinitely, even overnight, without an error message. Oh, and it can't be canceled. There is no pattern to when this happens and when it doesn't. I have resorted to installing every single package individually, and even then it freezes about 50% of the time and I have to restart the manager process. It just froze just now while I was typing that sentence.
Has anyone else had this problem?
Edit: I just realized that on my old machine, I used to have to check the box that says "Force https:// sources to be fetched using http://," but on this machine I haven't been forced to do that yet. Maybe that has something to do with it.
After unchecking "Force https:// sources to be fetched using http://" in the Settings view, I was able to download a number of updates without problems. It was only 6 updates, but some of them were fairly large and the whole process took a couple hours.
So, I'm going to tentatively mark this as the answer, so it can be referred to by SO users in the future. But if anyone else has this problem, please do try my solution and post a comment here saying whether or not it worked.
Unchecking "Force https:// sources to be fetched using http://" also solved the problem for me.
The solution that worked for me:
I'm copying this answer from http://code.google.com/p/android/issues/detail?id=21773
Steps:
stop and close sdk manager
go to the url http://innovator.samsungmobile.com/android/repository/repository.xml which was obtained from action log in sdk manager
<sdk:url>addon_samsung_GT_2.2_api-8_r01.zip</sdk:url> copy the zip file from the url field of xml doc (addon_samsung_GT_2.2_api-8_r01.zip) and replace repository.xml with the zip file name. The URL should be:
http://innovator.samsungmobile.com/android/repository/addon_samsung_GT_2.2_api-8_r01.zip
paste the url to your browser and download the file
copy the file to C:\Program Files\Android\android-sdk\temp folder
start sdk manager and re-select galaxy tab api and select install, it won't try to download and start immediately unpacking the file.
I guess it would be the same for other failing apis, docs, etc..
I was having the same issue on my Windows 7 x64 box. To get things to work I booted my computer into Safe Mode with networking. In safe mode I was able to load eclipse and use the adk manager to install everything.