Error with SDK package download in Android Studio

Question

java.io.IOException: Cannot download , response: 200 OK Warning: An error occurred while preparing SDK package Android Support Repository: Cannot downloa

Answer 1

Hi I faced a similar issue... Turn's out that may be related to system configuration of your machine..

Try downloading latest packages as per your system configuration from below:

https://developer.android.com/studio/?gclid=Cj0KCQjwj9LkBRDnARIsAGQ-hUfGD0_yGXcqqZBN6d1Y-nMZ-TNKZtvdRBHimcE8m0tPYjyUw_bV77AaAsdzEALw_wcB

Answer 2

I had this similar issue below worked for me. The solution for this is:

1. Run Android Studio as Administrator.

2. Re run the update.

It will work.

Answer 3

As shown in the android SDK video ./studio.sh has to be run, however if run without sudo or su, this might give problems like these. So you should run with sudo or su as shown below:

• sudo ./studio.sh(or /path/to/studio.sh)

or if you want to run as root

• su
• Password:root password
• ./studio.sh or (or /path/to/studio.sh) This should fix the problem There might be a problem with /tmp if it is on a different partition and the partition has less space than needed to install

Hope this helps.

Answer 4

I had the same problem, I downloaded problematic file 'https://dl.google.com/android/repository/emulator-windows-3833124.zip' and extracted it to C:\Users\$usrname$\AppData\Local\Android\sdk\extras\android. It solved the problem for me.

Answer 5

I had a similar issue while installing in Mac Catalina:

java.net.SocketException: Operation timed out (Read failed) Warning: An error occurred while preparing SDK package Sources for Android 29: Operation timed out (Read failed).

First attempt using standard configuration - Failed
Second attempt using standard configuration - Failed
Third attempt using Customer configuration, I selected the android simulator - Failed
Fourth attempt using Customer configuration, I selected the android simulator - Successful!

Not sure what was the reason, there is no change in any setting other than the above (and I am an Administrator of the Mac).

Answer 6

run the studio.sh script with sudo:

"sudo ./studio.sh"

if that does not work run:

"sudo chmod 777 -R /opt"

without quotes should work