Android Studio - No SDK Found - Setup wizard fails - Firewall Proxy

Issue

So getting right to the point, I am behind a corporate firewall. I had to manually download the zip file for Android Studio which I extracted to program files (windows 10) on my machine. When I launch studio I'm dialogue'd studio needs to retrieve sdk's which I try to do but it fails on these 3 zips.

build-tools_r29.0.1-windows.zip

platform-29_r01.zip

sdk-tools-windows-4333796.zip

Mostly I see

java.net.SocketTimeoutException: Read timed out Warning: An error occurred while preparing SDK package Android SDK Build-Tools 29.0.1: Read timed out.

I'm assuming my firewall proxy is preventing this type of setup install since the links to these zips point outside our network but I am able to download the zips individually through a browser session one by one and save them here

c:\Users\myPin\AppData\Android\Sdk

I extracted each zip file and then reran Android Studio but it doesn't seem to have made any difference. It still goes out trying to download the same packages which I already extracted to the SDK folder. Shouldnt studio see the zips I've extracted in the SDK folder location? How can I get this working?

Solution

So we have work around I think others might find useful. If your having problems with the Gui SDK manager, then definitely use the cmd based sdk manager. This did not time out for us.

So for example where in the Gui I would get something like

java.net.SocketTimeoutException: Read timed out

When tryin got get platform-29_r01.zip

But if I try to perform the same operation using C:\Users\PIN\AppData\Local\Android\Sdk\Tools\bin\sdkmanager.bat using whatever cmd tool you like (I like cmder).

.\sdkmanager.bat --proxy=http --proxy_host=access.lb.ssa.gov --proxy_port=80 "platforms;android-28" --verbose

The above cmd will dl's and configure the sdk correctly.

You may have to do this for any of the sdk's you require. I think in our Firewall proxy scenario there's a user-agent setting or something that is not set for the Gui which is causing the timeouts but not with the cmd tools so this is a legitimate work around I think.

Answered By - Puerto