An error occurred while updating the Android SDK using goagent.
Previously, it was okay to use goagent to update the android SDK, but it has always failed in recent months. However, it can be developed normally and does not matter much.
Updating the SDK in a home laptop always fails today. The following message is displayed:
INFO - [Nov 12 09:40:03] 192.168.0.189:49456 "AGENT CONNECT twitter.com:443 HTTP/1.1" - -ERROR - [Nov 12 09:40:03] ssl.wrap_socket(self.connection=<socket._socketobject object at 0x77056d50>) failed: [Errno 8] _ssl.c:504: EOF occurred in violation of protocolTraceback (most recent call last): File "/opt/etc/goagent/proxy.py", line 2237, in do_CONNECT_AGENTINFO - [Nov 12 09:40:03] 192.168.0.189:49457 "AGENT CONNECT twitter.com:443 HTTP/1.1" - - ssl_sock = ssl.wrap_socket(self.connection, keyfile=certfile, certfile=certfile, server_side=True) File "/opt/usr/lib/python2.7/ssl.py", line 381, in wrap_socketERROR - [Nov 12 09:40:03] ssl.wrap_socket(self.connection=<socket._socketobject object at 0x770655e0>) failed: [Errno 8] _ssl.c:504: EOF occurred in violation of protocolTraceback (most recent call last): File "/opt/etc/goagent/proxy.py", line 2237, in do_CONNECT_AGENT ssl_sock = ssl.wrap_socket(self.connection, keyfile=certfile, certfile=certfile, server_side=True) File "/opt/usr/lib/python2.7/ssl.py", line 381, in wrap_socket
After several passes, I finally found the answer in the goagent's Issue 18029.
Finally:
Xudong.s...@dianping.com in proxy. the [profile] Under ini can be updated with the following configuration android SDK dl-ssl.google.com = nofakehttpsOct 26,201 4 #2 the method mentioned above is indeed valid, you only need to add that line of tokens. But I don't know why the previous version of GoAgent does not need to do this step?
You only need to configure this.
Add the following configuration under [profile] In proxy. ini to update the android SDK.
dl-ssl.google.com = nofakehttps