IssueTracker

can you share your android studio version

Is this happening with Studio 3.0?

Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).

Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.

We have the same issue proxy uses NTLM, behaviour is the same like OP suggested (on Linux, Macs <-- I did not test windows yet)

Hi ! :-) same problem here. CI cannot be applied. Proxy is well configured in system, everywhere, but gradlew does not forward to sdkmanager when it is time to retrieve specific android dependencies. On Linux CentOS 7.

same issue here on our ci server. any updates so far?

Same issue for me on my ci server.
What I don't get is I can update the sdk with the command line just before, but the gradle plugin doesn't use what I downloaded.

I believe this should have been fixed by my change I61c3fc7edb044f3c72a96134bc54719f1957db63 on Jan 9.
Jerome, do you know in which release of gradle this was first available?

Unfortunately, I haven't had a possibility to check if it was fixed yet because there are some other reasons which prevent us from update to newer version of android plugin.
I'll confirm the fix as soon as we will manage to update it on our side.

Any news?
Thanks.

We've just updated android plugin up to 2.3.3.
The issue is still valid: gradle downloads 3rd-party libraries like gradle itself or kotlin, but fails to download required parts of SDK. We tried to specify its proxy settings via gradle.properties and through command-line.

Probably it could be caused by the fact that there was a big change in android tools 25 infrastructure, so it doesn' read ~/.android/androidtool.cfg anymore...

if you use proxy and have https tunneling this was disabled (for various reasons by oracle) I would suggest you enable it with:
in gradle.properties
org.gradle.jvmargs="-Djdk.http.auth.tunneling.disabledSchemes=''"

and try again, cheers

Unfortunately, this measure doesn't help.

Downloading with sdkmanager (and passing http proxy settings as its parameters) works just fine.

Joe the first build that contained the fix is mentioned above is 3615235 which is prior to 2.3.3 release which 4069837.

so it seems that the bug is not completely fixed.

I face the exact same issue. I reported it here https://stackoverflow.com/questions/44929694/gradle-not-able-to-download-andriod-packages/45938233#45938233

Is there a plan to fix this?

Can I confirm what the workaround to this is? Is it as per #5? Download the missing dependencies manually?

I assume this also means that the CI server requires AS installed and the ability to open it (an XServer)? Or can I do this exclusively from the command line?

You can do it manually using sdkmanager tool located in <Android SDK >=
25>/tools/bin/sdkmanager . Don't forget to provide your proxy settings.

2017-08-30 15:24 GMT+03:00 <buganizer-system@google.com>:

Great your site. When i view your article and view your site have good.
I like your site.I have feel good in your content the best.
Article have good on cyber world.

Thank for sharing article.  
http://www.sinidomino.com/
http://jejakaktual.blogspot.com/

Updated from command line as mentioned in #21 but still am unable to run my CI build.
did it work for anyone?

As it stands now, the proxy settings are taken from http.proxyHost / http.proxyPort or https.proxyHost / https.proxyPort system properties. Adding them to your JVM args (e.g., in gradle.properties) is the supposed solution. So if the names of the parameters in your configuration match the above and it still doesn't work as expected - please get back to us.

(Also as a FYI, in the context of SDK manager, we've improved proxy support with fixing b/79122663 - so if your system has the proxy environment variables defined, the SDK manager CLI will pick up those settings. In that case, one of the options applicable on CI is to add an SDK manager CLI invocation prior to build, e.g.: ./sdkmanager --update).

Please let us know if we can assist further on this issue.

This documentation page might be helpful as well: https://developer.android.com/studio/intro/studio-config#gradle-plugin

Marking as fixed now, but please do let us know if the information in the documentation provided above doesn't solve the issue.