| |
Cause:
To do with the Android Android development, when installed after the ADT (Android Deveopment Tooling) (refer to the previous "[Android] Eclipse installation ADT [Android Development Tooling] failure of the two solutions"), the next meeting To the Android SDK Manager can not update the problem, because GFW relationship, can not directly access https://dl-ssl.google.com, the problem is more serious than the update ADT. In the previous article, we set up the proxy http://127.0.0.1:8087 to go to the GoAgent to access the ADT update address, where we encountered a new problem, because the GoAgent from 3.1.x version, For https: // or SSL access will be such an error:
Error: [( 'SSL routines', 'SSL3_READ_BYTES', 'sslv3 alert certificate unknown')]
This will prevent Android SDK Manager from updating properly.
In the past, it may be done, that is, in the Android SDK Manager from the Tools menu, select Options ..., according to the following settings can be (see the red line of a single option):
That is mandatory to use http: // instead of using https: //, but now because of the new version of GoAgent reasons (v3.2.3), will report the error mentioned earlier, which can not be updated.
Using VPN or other scientific Internet updates
Since the normal update and use GoAgent will not work, then we can think of a scientific approach to the Internet, "Android sdk manager can not update the solution", set up, you can download, but the speed is a bit slow
Speed is about 10-40 KB / s or so, the update can be updated, but think about so many packages to be updated, to download to the monkey on ah, so we have to find another way, if you have a fast and free VPN, When I did not say anything.
Resolve GoAgent issues
Since GoAgent error, we find a way to solve this error, this is not very good to find, I did not find the beginning, but read the above download speed, I decided to solve it. Issue 17951: sslv3 alert certificate unknown and Issue 17116: the use of GAE can not be agents to upgrade Android SDK, the solution is: do not have to worry about,
3.2 version In the proxy.ini in the [profile], add the following configuration to update the Android SDK:
Dl-ssl.google.com = nocrlf, noforcehttps, nofakehttps
Note: There is a prerequisite, you must ensure that the GoAgent CA certificate is imported (after you update the GAE GoAgent or local GoAgent version, you may want to re-import the certificate), the specific import method can see To the Issue 17951 in the introduction, or their Google.
The specific cause of this error is unknown, from the literal meaning of the solution, nocrlf (no carriage return linefeed), noforcehttps (no mandatory use of https), nofakehttps (do not use / does not allow false https). Anyway, so now
More than 500 KB / S is basically the speed limit of my broadband, pretty good, although sometimes GoAgent will slow down, but most of the time the speed is still possible, free to this, has been very satisfied.
Problem-solving, I hope to help you. |
|
|
|