I had same issue with the latest Android Studio () today, and I finally found that configuring a https proxy for Gradle can solve the issue. I only set a http proxy at the beginning. Gradle needs to sync some files via HTTPS. Use IP address instead if hostname of proxy can't work.

This problem happens when we work with android sdk studio different from what you should do is install Android Support Repository https://sites.google.com/a/android.com/tools/knownissues

The IDEA official documentation is clear about that : Share all the files under .idea directory in the project root except the workspace.xml and tasks.xml files which store user specific settings, also share all the .iml module files. Source : How to manage IntelliJ IDEA projects under Version Control Systems EDIT : But, sharing iml files seems to be wrong. Best thing is to use a similar gitignore file and to import the project in AndroidStudio for each developer.

do the eclipse step where you export to generate the gradle build file stop importing your project for now and create a new one. close android studio. navigate on your file system to the new project. take the "gradle" folder in there and copy it in to your project. try again. :-)

you might want to make your Dir a own module add include 'Dir' to your settings.gradle create a build.gradle inside your Dir directory with this content apply plugin: java now you can go into your main projects build.gradle and add to dependencies: compile project(':Dir') if your Dir uses android related stuff, you might want to use the New > Module(right click on your project in Android Studio) Function of Android Studio to create an Android Library. But i haven't tested that feature yet. If Android Studio throws an Exception when trying to use the New Module, you should try to update Android Studio, in the latest Version it works for me. You might also want to check the Gradle User Guide and the DSL Reference both are very helpfull in getting into Gradle and understanding i

After some further reading and several false starts, I ended up with this, added to the bottom of build.gradle in the project directory (that is, MyAppProject/MyApp/build.gradle, not MyAppProject/build.gradle -- confusing, I know, but the former directory is projectDir in Gradle so that's how I refer to it here). It depends on no external utilities other than Git, which is assumed to be in the path, so it should work on any OS (even though I used forward slashes in the paths, they get converted to backslashes on Windows). It could probably stand to be improved, I'm sure, as my understanding of Gradle is pretty rudimentary and my Groovy may not be very idiomatic (though that in particular is less of a concern). I have a feeling that my approach is suboptimal because it involves generatin

i think this tutorial will help you : http://cyrilmottier.com/2013/06/27/a-productive-android-development-environment/ !

You should create a folder in you project's root and name it libs. Then copy your jar file to that folder and add dependencies { compile fileTree(dir: 'libs', include: '*.jar') } to your build.gradle file. If above won't work. You may need to try this post

You should look at the multiproject example for the layout attached in the doc. http://tools.android.com/tech-docs/new-build-system http://docs.google.com/viewer?a=v&pid=sites&srcid=YW5kcm9pZC5jb218dG9vbHN8Z3g6NDYzNTVjMjNmM2YwMjhhNA Essentially you want a top level settings.gradle that tie all the pieces together. Ideally they should be in one single git repo to make your life easier. However you probably can use symlink to tie them into a common build repo that contain your top level settings.gradle.

I don't know how to solve your problem, but when I faced problem of third party library use in Gradle build, I solved by following way. Following is my structure of project. GsonDemoProject    GsonDemo       build       libs           android-support-v4.jar           gson.jar       src           main           build.gradle       build.gradle       settings.gradle I edited my build.gradle file which resides in src directory.

You can use: compile 'com.nineoldandroids:library:2.4.0+' or if you have the library copied to your project libs directory, you can use: compile files ('libs/ nineoldandroids-2.4.0.jar') however, you can check out my post on getting started with swipelistview: http://modewagon.wordpress.com/2013/09/16/getting-started-with-swipelistview/

Your build.gradle is trying to use Android SDK tools 8 which isn't installed on your machine. If you look at your build.gradle file you probably have this line buildToolsVersion "8". You want your build.gradle file to point to the Android SDK tools that you currently have installed (preferably the latest). Just open the Android SDK manager and see which tools you have installed and change the buildToolsVersion "8" to the right version.

Go back to Project Structure window where you added the new module. Click on your main module, go to Dependencies tab, click the plus icon and select Module Dependency.

Do not add modules through the Studio interface. Always make the changes directly in build.gradle and then reimport into Studio. Also, update the plugin dependency to com.android.tools.build:gradle:0.4.+ to get the latest 0.4.* version.

I just ran into this problem when moving to a new computer. What I did was choose to import a project (using build.gradle as import file) rather than open a project. When prompted about gradle information I didn't supply a gradle home but selected to use the gradle wrapper.

Right click on project - Select "Open Module Settings" - Select "Modules" in left pane - Click on "+" symbol on top - Choose "Import Module". After importing Module. You need to add it as a dependency for your current project. Keep "Modules" Selected in left pane and click on your project - Now Go in dependencies tab and click on "+" symbol that is located at bottom - Choose third option "Module Dependencies" and if you have imported your project correctly, it will show you the all available module that can be added as a dependency to your current project. Hope it would help. Cheers!!

All you need is a simple build.gradle file for your ActionBarSherlock project. Here's one I've created: buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:0.4.2' } } apply plugin: 'android-library' dependencies { compile 'com.android.support:support-v4:13.0.0' } android { buildToolsVersion "17.0" compileSdkVersion 17 sourceSets { main { manifest.srcFile 'AndroidManifest.xml' java.srcDirs = ['src'] resources.srcDirs = ['src'] aidl.srcDirs = ['src'] renderscript.srcDirs = ['src'] res.srcDirs = ['res'] assets.srcDirs = ['assets'] } } }

you need to declare a repository where you want to resolve the commons-io library from (e.g. MavenCentral): buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:0.5.+' } } apply plugin: 'android' repositories{ mavenCentral() } dependencies { compile files('libs/android-support-v4.jar') compile group: 'commons-io', name: 'commons-io', version: '2.0.1' }

I finally found out why this didn't work. There are two ways to include a project from within the settings.gradle file: include ':..:source:compA-api' and include "source:compA-api" project(':source:compA-api').projectDir = new File(settingsDir, 'source/compA/api') I had used the second form and apparently Android Studio didn't like that :)

You have used Gradle 1.8, as your error mentions, you should use Gradle 1.6. Download it from here http://services.gradle.org/distributions-snapshots

Managed to solve on my own. Needed to alter the build.gradle file a bit so the buildscript->dependencies will hold this: classpath 'com.android.tools.build:gradle:0.5.+' and not: classpath 'com.android.tools.build:gradle:0.4' Then used the "local gradle distribution" option with the 1.6 version I downloaded and it worked fine.

As the others say, a full import is not possible, but just try a manual 'import'. The key files for an Android project are the Java sourcecode (src directory), the resource XML files and the Manifest. Just create a new Android project in Eclipse and simply copy these files over. You may have to create a new package structure, so construct the necessary packages and copy each sourcefile over and refactor the package name if necessary. If you use any additional libraries, you may have to manually import them as well.

Well I managed to solve it after many hours of trying. First of all I use Windows 7, with 16GB ram, and it was the system path that was truncated! This left me without the proper GRADLE_HOME path. I manually downloaded the latest Gradle-1.7 build. Android studio 0.2.3 was using 1.6, but subsequently to my manual fix 0.2.5 uses Gradle-1.7. I created a System variable: GRADLE_HOME with value: D:gradle-1.7 that points to my manual Gradle install. I broke my 'real path' (before windows truncated it) into 'extended' path variables, thus shortening my actual path, and inserted the following at the end of the path: %GRADLE_HOME%/bin;%JAVA_HOME%/bin; There are many links on dealing with truncated windows path on stackoverflow. And that was all that was required to get it working. Hope I can

I want to answer my own question after I found out recently. If we have module B need module A library. apklib is create as a library and can be use and read from maven to reference. So if set module A in maven's pom.xml dependency, when mvn build it will ask maven to look for apklib. And as IntelliJ and Android Studio, just go to project structure set the module to Android Library, and add module dependency, then like module B can use from module A.

It's a nice warning not error, to see the complete lint report you can add these lines to build.gradle: allprojects { tasks.withType(JavaCompile) { options.compilerArgs << "-Xlint:deprecation" } } If you really want to get rid of those warnings: Don't use deprecated API Use @SuppressWarnings("deprecation")

Thank you, I have resolved this problem already. The cause of this error is really surprising. If you try to download Gradle using 3G connection, it will always fail, that is at least in my case. When I connect using DSL connection Android Studio directly start to download Gradle with no problem and I am able to create new project. Now even if I switch back to 3G connection it is still working. So to replicate my scenario, try to download Gradle using 3G connection or install brand new Android Studio installation using 3G connection. I hope this will help someone. NOTE: My 3G connection speed is better than my DSL connection.

While migrating your project from Eclipse to Android Studio, no change have been done on project structure. The only that have changed are new .iml and .gradle files. Your java code stays in project/src/ folder, and has not been moved in project/src/main/java folder (like in a new created project from AndroidStudio). Your AndroidManifest file also stays in the project/ folder and has not been moved in project/src/main/ folder (like in a new created project from AndroidStudio). At migration, the build.gradle file is customized in order to be able to compile with the old structure is described in the gradle documentation : Configuring the Structure For a new created project in AndroidStudio, the sourceSets part of the build.gradle file : sourceSets { main.java.srcDirs = ['src/java']

You just need to add "@string/abc_action_mode_done" in your appcompat/res/values/strings.Do not "set mediarouter as a dependency for appcompat library".(In my case,"@string/abc_action_mode_done" already exists in the appcompat/res/values/strings.I don't know why you miss it.) "add depenency appcompat to mediarouter" is necessary.

You should try updating/upgrading your build tools and gradle through AndroidStudio. Once you do this, or if you have already done it, you should be able to modify your build file to reflect the updates: classpath 'com.android.tools.build:gradle:0.5.+' ... buildToolsVersion "18.0.1" NOTE: I am still unable to generate aar files even with this setup, although compiling is fine. At least this might get you past this hurdle.

Okay, I fixed the issue. It was quite weird. A) I had some capital letters in my res/drawables folder. Not too weird -- I can see how that would remove the first error. B) Then, however, a lot of values in my main activity file became undefined. I had to manually import 'com.myapp.R'. Now that was weird. Fortunately, everything is now working. I hope that if anyone gets the same errors as me, that this response can help them.

Look at this links. How do I open my existing Eclipse projects in Android Studio? http://developer.android.com/sdk/installing/migrate.html

You may want to review the steps this link. It goes through the steps of adding it to your Android project, regardless of your IDE. Eclipse will work just fine. These steps take some time and effort, but I have successfully done this before.

This is because one or more of your asset names have unsupported characters present. Replace all capitals with lowercase letters. Replace all spaces and dashes with an under-bar/underscore. AND to be safe, remove all numbers too. Another suggestion I've seen going around is to make sure your SDK is up to date, but from my own experience it has always been the names of imported assets.

This google group has an answer from Android SDK developer Xavier Ducrohet. https://groups.google.com/forum/#!topic/adt-dev/bPY_Un8BsBY To quote: To depend on a gradle project that's outside of your main project's root folder you can try to do the following: include 'abs' project(':abs').projectDir = new File('/some/path/relative/or/absolute') Note that your app should do a dependency using project(':abs'), since the gradle path is :abs no matter what the on-disk path is.

The manifest files for the library must currently have a <application /> node, even if it's empty. It's a restriction we'll remove at some point but for now, just add it.

From your screenshot, settings.gradle is inside TestProjectProject, which makes TestProjectProject a root project. However, java-ws-client is parallel TestProjectProject, which is outside of TestProjectProject's scope. You cannot reference any project outside its scope using ":foobar" notation. To fix the second problem, you should either move java-ws-client into TestProjectProject, or declare java-ws-client as an external dependency, and add proper repository resolver to find it. To fix the first problem, make sure in TestProjectProject/build.gradle you have applied the Java plugin. The Java plugin creates the "default" configuration.

The steps in the link you specified should also work for Android Studio. Just make a copy (using a file manager) of the entire module folder and give it a new name. Now open it up and use Refactor -> Rename (right click on the item you want to rename) to rename your module and package. See this for details about refactoring in IntelliJ/Android Studio.

At current, Android doesn't support Java 7, only Java 6. New features in Java 7 such as the diamond syntax are therefore not currently supported. Finding sources to support this isn't easy, but I could find that the Dalvic engine is built upon a subset of Apache Harmony which only ever supported Java up to version 6. And if you check the system requirements for developing Android apps it also states that at least JDK 6 is needed (though this of course isn't real proof, just an indication). And this says pretty much the same as I have. If I find anything more substancial, I'll add it. Edit: It seems Java 7 support has been added since I originally wrote this answer; check the answer by Sergii Pechenizkyi.

It warns you that android plug-in task validateDebugSigning cannot access the debug key. Check your accessibility to the debug.keystore. On linux or OS X, the default location is ~/.android. On windows, it's in C:Documents and Settings.android or C:Users.android.

You missed the sample comments. versionName getVersionName.output() should work. EDIT: Change your task code to the following. task getVersionName(type:Exec) { exec { commandLine '../scripts/version-name.sh' } ... } I am also new to gradle, it seems they have some bugs or the documentation is lacking. Since the code you had tried out is exactly from the sample, available in the document.