Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Android Studio setup wizard cannot download the SDK add-on list

ErrorUnable to access Android SDK add-on list

Short answer

The setup wizard and SDK Manager need internet access. Behind a firewall, set the proxy in Android Studio's HTTP Proxy settings, not only in gradle.properties, because the IDE setting overrides it. If the log says peer not authenticated, the Java certificate store lacks the proxy's certificate.

  • Applies to Android Studio (current stable), Windows 11, macOS 15, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check whether the machine can reach the SDK repository at all from a terminal. If a direct connection works and Android Studio's does not, the problem is proxy or certificate handling inside the IDE.

    curl -I https://dl.google.com
  2. 2Match what you see, then jump to its fix

    1. 1The wizard fails on a network that only allows internet through a proxy.The IDE has no proxy configuredFix
    2. 2Gradle builds download through the proxy but the wizard and SDK Manager still fail.The proxy is set only in gradle.propertiesFix
    3. 3peer not authenticated in the log from Gradle sync or the SDK ManagerJava does not trust the proxy's certificateFix

What does the error look like?

  • Unable to access Android SDK add-on list
  • peer not authenticated

Cause 1 of 3

The IDE has no proxy configured

1Check

Open the proxy page: Settings (Android Studio, Settings on macOS) then Appearance and Behavior, System Settings, HTTP Proxy.

# Android Studio: File > Settings > Appearance & Behavior > System Settings > HTTP Proxy

2Fix

Choose Auto-detect proxy settings, or Manual proxy configuration and enter host and port, then Apply. The docs note that Android Studio requires an internet connection for the Setup Wizard.

# Manual proxy configuration: host name, port number, then Check connection

3Verify

Reopen the SDK Manager (Tools, SDK Manager) and confirm the package list loads.

# SDK Manager lists platforms and tools

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 3

The proxy is set only in gradle.properties

1Check

The IDE's HTTP Proxy page overrides gradle.properties inside Android Studio, so a proxy set only there does not help the IDE tools.

grep -n "systemProp" gradle/gradle.properties ~/.gradle/gradle.properties

2Fix

Enter the same proxy in the IDE settings. Keep the systemProp.http and systemProp.https entries in gradle.properties for command-line and CI builds.

# gradle.properties (command line and CI)
systemProp.http.proxyHost=proxy.company.com
systemProp.http.proxyPort=443
systemProp.https.proxyHost=proxy.company.com
systemProp.https.proxyPort=443

3Verify

Run Check connection in the IDE proxy page.

# HTTP Proxy page: Check connection

Confirmed by developer.android.com

Did this fix it?

Cause 3 of 3

Java does not trust the proxy's certificate

1Check

The docs say the root cause is a missing certificate in the JDK's cacerts file. Test with a direct connection first to rule out the proxy.

curl -I https://dl.google.com

2Fix

If you are behind a proxy and a direct connection works, add the proxy's certificate to the cacerts keystore with keytool. On Ubuntu, an empty cacerts file is a known issue and is fixed by reconfiguring ca-certificates-java.

keytool -importcert -alias corp-proxy -file proxy.cer -cacerts
# Ubuntu, empty cacerts:
sudo /var/lib/dpkg/info/ca-certificates-java.postinst configure

3Verify

Sync a project or open the SDK Manager again.

# SDK Manager loads without peer not authenticated

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • Set the proxy in the IDE and in gradle.properties on any machine behind a firewall.
  • Ask the network team for the proxy certificate before first install.
  • Install from the full download rather than relying on the wizard when the network is restricted.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

adb tcpip 5555 fails because no device is found

adb: more than one device/emulator

adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.