How do I manage changing SNAPSHOT dependencies with Android Studio? - android

I'm using Android Studio 0.2.5 with gradle 1.6. I'm collaborating with a developer of a library I'm using, so when he pushes updates to some-library:2.1.5-SNAPSHOT I'd like to get it immediately. I can disable caching for changing modules in gradle by setting the resolution strategy as follows:
configurations.all {
resolutionStrategy.cacheChangingModulesFor 0, 'seconds'
}
This works fine for command line builds, but it looks like Android Studio is still using the old version of some-library-2.1.5-SNAPSHOT. The only workaround I've been able to get to work is to delete myproject.iml and the .idea directory and re-import into Android Studio, which is very time consuming and seems unnecessary.

Another workaround is to delete the ~/.gradle/caches directory and then sync the project in Android Studio.
This is not ideal since all your dependencies need to be re-downloaded, but its a little less intrusive that re-importing the project into AS as noted by #Joe.
Terminal: rm -rf ~/.gradle/caches
AS: Tools > Android > Sync Project with Gradle Files (or hit the "Sync Project with Gradle Files" menu button)
EDIT
Did some more researching and found this little gem.
Just configure your dependency as such...
compile ('groupId:artifactId:X.X.X-SNAPSHOT'){
changing=true
}
Then just run gradle clean assemble on the project that has the SNAPSHOT dependency.
I did test to see if a newly added constant became available, and sure enough it worked.

Related

gradle error in unity exported android project

I am going to use the build config property "multiDexEnabled true" to break 64K methods limit following link
https://developer.android.com/studio/build/multidex.html#about
I update to use unity 5.6.1f1 and android studio 2.3.3. I set "build system" option to "Gradle(New)", which is new added from 5.5, then click "Export" to create an android project.
I open the exported project with android studio, then I get the following error
I try the two blue links, but I keep geting this same result.
For my unity project, I only create an empty project and add a button to a unity scene, then export it. I have also tried to build API directly, it works.
It is important for me to export unity project to andoid studio project, because it can help us to use additional compile options
Do any one know what I miss? Or how to export unity project correctly?
Thanks
The gradle error text, if cannot see the image link
Error:org.gradle.api.internal.tasks.DefaultTaskInputs$TaskInputUnionFileCollection cannot be cast to org.gradle.api.internal.file.collections.DefaultConfigurableFileCollection
Possible causes for this unexpected error include:Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)
Re-download dependencies and sync project (requires network)The state of a Gradle build process (daemon) may be corrupt. Stopping all Gradle daemons may solve this problem.
Stop Gradle build processes (requires restart)Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project.In the case of corrupt Gradle processes, you can also try closing the IDE and then killing all Java processes.
I had the same issue with unity 2017.1.0b4 and Android Studio 2.3.3, gradle 3.3.
You should change android plugin for graddle version in Android studio to 2.3.3
You can specify the Android plugin for Gradle version in either the
File > Project Structure > Project menu in Android Studio, or the
top-level build.gradle file. The plugin version applies to all modules
built in that Android Studio project. The following example sets the
Android plugin for Gradle to version 2.3.3 from the build.gradle file:
buildscript {
...
dependencies {
classpath 'com.android.tools.build:gradle:2.3.3'
}
}
https://developer.android.com/studio/releases/gradle-plugin.html
Check your local gradle version in directory -
C:\Users\yourname\.gradle\wrapper\dists
Modify your project gradle configuration -
project\gradle\wrapper\gradle-wrapper.properties
distributionUrl=https\://services.gradle.org/distributions/gradle-3.3-all.zip
Make sure gradle-3.3-all match to your gradle version.
If you have wasted a lot of time fixing unity Gradle error but nothing worked then you tried unity internal builder but that gave "Parsing Package error"
then try this, it will not help you make your project using unity's Gradle but it will make your project without any error successfully.
Export your project from unity to a folder eg: ProjectName_Gradle.
open android studio, make sure you are connected to the internet .
close current project then select "Open Gradle, eclipse ADT, etc;" option and open ProjectName_Gradle folder.
check the version of buildTools installed in your android-SDK by opening android-SDK settings from the android studio itself.
edit "build.gradle" file under Gradle Scripts section or under your project.
and change "buildToolsVersion" to the latest version installed in your SDK.
then click "syn project with Gradle Files" from file option and let it sync.
it may ask to update Gradle version, then click update
now there should not be any errors.
now try building APK.

Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)

I am getting this kind of error, how to fix it.
Error:Unable to load class 'org.gradle.tooling.internal.protocol.test.InternalTestExecutionConnection'.
Possible causes for this unexpected error Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)
Re-download dependencies and sync project (requires network)The state of a Gradle build process (daemon) may be corrupt. Stopping all Gradle daemons may solve this problem.
Stop Gradle build processes (requires restart)Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project.In the case of corrupt Gradle processes, you can also try closing the IDE and then killing all Java processes.
I updated my Android Studio to 2.3 and it asked me to update my gradle plugin to 3.3 that created issues with my running projects.
I've gone through all the Stack solutions and nothing worked for me except this workaround:
I changed my distribution url in gradle-wrapper.properties with this one.
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.2-all.zip
(permanent link list here : https://services.gradle.org/distributions/)
My project is up and running.It just asked me to update to gradle build tools 25.0.0 which I did so. Everything is fine now :)
Go to the project section and select gradle scripts menu.
Under script, menu select gradle -wrapper.properties
Then replace the distributionUrl=https://services.gradle.org/distributions/gradle-2.2-all.zip with "distributionUrl=https://services.gradle.org/distributions/gradle-3.4.1-all.zip"
note: distributions gradle will change depended upon the version of the android studio.
Make sure you have Internet Connection then:
1.For Window Users Go to > C:\Users\username\.gradle\wrapper\dists
2.For Linux users
Go to $HOME/.gradle (~/.gradle) and/or (Under Specific project)
<PROJECT_DIR>/.gradle
3.Delete the gradle file(s) with the problem(i.e the zipped folders with
missing with no its extracted file )
4.Sync the project with gradle files.
Delete corrupt files
This error occurs when Gradle files are not completely downloaded or corrupted by some other reason, so we have to redownload the files.
The easy way is to delete the old files in
C:\Users\username.gradle\wrapper\dists
and rebuild the project, Android Studio will automatically download the new files.
Watch the Tutorial
https://www.youtube.com/watch?v=u92_73vfA8M
or
follow steps :
Go to any browser
type gradle and press enter
you can specify any version you want after the
gradle keyword
i am downloading gradle 3.3
https://services.gradle.org/distributions
click on this link which is in description directly if you want
click on gradle 3.3 all.zip
wait for the download to complete
once the download is complete
extract the file to the location
c://user/your pc name /.gradle/wrapper/dists
wait till extraction it takes 5 mins to complete
Now open your project in android studio
9.go to file > settings >bulid ,exec,deployment > gradle
now change use default gradle to
use local gradle distributn
select the location where you had extracted gradle 3.3.zip
C:\Users\your pc name.gradle\wrapper\dists\gradle-3.3
click on OK
Now build starts again and
you can see now the build is successful and error is resolved
If you manually setup gradle also make sure projects build.gradle verison is compatible with it. See following as an example.
Project's build.gradle
dependencies {
classpath 'com.android.tools.build:gradle:2.3.2'
}
Manual gradle setup
A lot of answer to this questions but a few were helping. I want to give accurate and updated answer.
Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)
This error happens when you bad internet connection or you put your computer to sleep while Android Studio is downloading the required dependencies.
How to resolve this issue.
Find out the project's Gradle version. You will find that in gradle-wrapper.properties in distributionUrl my gradle distribution was https\://services.gradle.org/distributions/gradle-6.5-all.zip that means gradle-6.5-all.zip is required to download and right now it is corrupted because of connection timeout. Lets find out this folder and delete this.
Go to $HOME/.gradle folder then to wrapper then to dists then find a folder that matches the gradle version name that required to download. In my case it was gradle-6.5-all.zip select this folder and delete it.
Now sync the project and make sure you have good internet connection and setting that will prevent your system going to sleep while downloading something.
Kindly delele all folders under the in /.graddle/version/
This is how i solved mine. good luck
Maybe you can run ./gradlew build -s in the terminal, the stacktrace would show you where went wrong.
Try the next step to "Refresh" your IDE (android studio)
1. Let Gradle rebuild your auto-genrated files by click Build | Rebuild
2. Also try Choose File | Invalidate Caches/Restart.
I resolved this issue by downloading current version of graddle from link given
download latest version of graddle possibly graddle 3.3
Then in next step i accessed .graddle/wrapper/dists dirctory from home directory on my Mac after showing up hidden system files and deleted previuos version folder residing there.
Now i put that downloaded latest version folder after uncompressing there.
Now restarted Android studio and problem was resolved.
If you are seeing this error in Android Studio 4.1 with Gradle 6.5 then you should move back to
classpath 'com.android.tools.build:gradle:4.0.2'
For some reason
classpath 'com.android.tools.build:gradle:4.2.0'
does not work correctly.
You can try this
first Open your Android Studio > open any project you're doing
click on File > Settings > Build,Execution,Deployment > Gradle
At Project-Level settings , there are 2 option to sync the gradle either usin the default or local.
now change from default to a local gradle distribution > gradle Home
select the path on your computer.
C:\Program Files\Android\Android Studio\gradle\gradle-4.1
click on OK
Now build starts again it should be solved.
Go to "C:\Users\.gradle\caches\". Delete all the files in the folder. Then Sync Gradle and Rebuild the project.
i deleted the gradle folder and then i did rebuild, every thing working fine
If you using Ubuntu, So firstly you have unhide all files from your home directory or where located your android studio folder :
Go to your home directory and unhide all files by using ctrl+h
You found .gradle folder
Inside .gradle -> wrapper
You can found dists folder, So delete this dists folder
Create a New Project than your Gradle file re-downloaded
Congo you successfully build project
check out distributionUrl setting in gradle-wrapper.properties. I changed https to http, then my problem was solved.
In my case,just change http to https in the gradle-wrapper and Sync it.
Just reimport project. :)
I tried cleaning up the cache and refreshing dependencies doesn't work but failed.
Clear .gradle folder and rebuild
Open C:\Users\Username.gradle\wrapper\dists\
Open latest gradle folder, e.g. gradle-4.1-rc-1-all
You will find a random folder named 936kh1brdchce6fvd2c1o8t8x
Download zip file of similar name
eg: https://downloads.gradle.org/distributions/gradle-4.1-rc-1-all.zip
Save it in this folder
Restart Android studio
It will automatically extract the zip folder and Error will clear
Finally solved this problem.
If you just copy new version's files to old folder and override files,you may face the same question as me.
To solve it:
makesure you saved your all settings.
close AS,DELETE ALL files of your mixed version.
extract new version to your empty folder.
It works for me.
For me, i was cloning a project from github which used a version of gradle higher than that which i had installed. I had two choices:
Open gradle.wrapper-properties of a project you have that's building successfully, and copy the line that says distributionUrl=https\://services.gradle.org/distributions/gradle-4.10.1-all.zip. Use this to replace the same value in the project that's failing. That should do the trick.
Your build might still fail if the gradle version used to build the project is higher than that which you just added. For this you should update the gradle version to the latest.
In my case I hade to change from:
plugins {
id 'com.android.application'
id 'kotlin-android'
id 'kotlin-kapt'
**apply plugin :'com.google.gms.google-services'**
}
to
plugins {
id 'com.android.application'
id 'kotlin-android'
id 'kotlin-kapt'
id 'com.google.gms.google-services'
}
search on google "download java 11"
click oracle website download your java to your platform and install it.
go to android studio click CTRL+SHIFT+ALT(Project Structure)
SDK Location Tab Show the path of JDK location which you installed
In your gradle-wrapper.properties
distributionUrl=https\://services.gradle.org/distributions/gradle-6.5-bin.zip
This won't download and always gives 'gradle cache corrupt' error, but a small change makes it work fine
distributionUrl=https\://services.gradle.org/distributions/gradle-6.5-all.zip
Now sync the gradle again and it's done.
I will generalize the issue that you might face
Inside module's build.gradle :
Change:
plugins {
[...]
apply plugin:'whatever_you_have'
}
to
plugins {
[...]
id 'whatever_you_have'
}
In other words instead of apply plugin: use id
Unable to find method ''void
com.android.build.api.extension.AndroidComponentsExtension$DefaultImpls.androidTest$default(com.android.build.api.extension.AndroidComponentsExtension,
com.android.build.api.extension.VariantSelector,
kotlin.jvm.functions.Function1, int, java.lang.Object)'' 'void
com.android.build.api.extension.AndroidComponentsExtension$DefaultImpls.androidTest$default(com.android.build.api.extension.AndroidComponentsExtension,
com.android.build.api.extension.VariantSelector,
kotlin.jvm.functions.Function1, int, java.lang.Object)'
Gradle's dependency cache may be corrupt (this sometimes occurs after
a network connection timeout.)
Re-download dependencies and sync project (requires network) The state
of a Gradle build process (daemon) may be corrupt. Stopping all Gradle
daemons may solve this problem.
Stop Gradle build processes (requires restart) Your project may be
using a third-party plugin which is not compatible with the other
plugins in the project or the version of Gradle requested by the
project.
In the case of corrupt Gradle processes, you can also try closing the
IDE and then killing all Java processes.
It happened to me after upgrading Android Studio to 4.2.0.
Updating the hilt classpath on build.gradle to 2.35 fixed these issues for me.
classpath "com.google.dagger:hilt-android-gradle-plugin:$2.35"
If you have updated your android studio, then go to FILE, Project Structure, Project, then check gradle version. Before that check your gradle version in C:\Program Files\Android\Android Studio\gradle and check the version if it matches then sync again else change the gradle version in android studio and sync again.
I had a similar problem after cloning AnySoftKeyboard and opening it in Android Studio. What worked for me was deleting the AynSoftKeyboard/gradle folder and then cleaning the project via menu item Build > Clean Project.
So try deleting YourProject/gradle folder and clean the project to trigger a Gradle sync.
Hope it works for your case.
download gradle from here for your OS and extract the file and paste the inner folder into installLocation/gradle
than in Android Studio Goto File > Settings > bulid ,exec,deployment > gradle and choose local gradle option and provide the file path of your new downloaded gradle and hit ok it works :)

Android Studio build fails with "Task '' not found in root project 'MyProject'."

I get this error when trying to build my project after changing laptop and updating to Android Studio version 0.8.2.
FAILURE: Build failed with an exception.
What went wrong:
Task '' not found in root project 'MyProject'.
Try:
Run gradle tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Here are my Gradle files:
Top Level settings.gradle
include ':MyProject'
build.gradle in MyProject:
apply plugin: 'com.android.application'
buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath "com.android.tools.build:gradle:0.12.+"
}
}
repositories {
mavenCentral()
}
android {
compileSdkVersion 20
buildToolsVersion "20"
defaultConfig {
minSdkVersion 14
targetSdkVersion 20
}
}
dependencies {
compile 'de.timroes.android:EnhancedListView:0.3.0#aar'
compile 'com.nineoldandroids:library:2.4.0'
}
Top level build.gradle is empty
Though late in answering, this is a hard one to Google (the single quotes) and it’s not clear what’s happening. I don't have the reputation yet to comment or ask for scope (or post 3 links), so this answer may be a little tedious.
To answer fast, you may have multiple Gradle plugins in your project.
Synchronize Gradle Wrapper and Plugins
My issue seemed to start with a corrupted IML file. Android Studio (between closing and reopening a project) began complaining an IML was gone (it wasn’t) and a module should be deleted, which I declined. It persisted, I upgraded to AS 0.8.7 (canary channel) and got stuck on the OP issue (Task '' not found in root project). This completely blocked builds so I had to dig in to Gradle.
My repair steps on OSX (please adjust for Windows):
Upgrade Android Studio to 0.8.7
Preferences | Updates | Switch "Beta Channel" to "Canary Channel", then do a Check Now.
You might be able to skip this.
Checked the Gradle wrapper (currently 1.12.2; don’t try to use 2.0 at this time).
Assuming you don’t need a particular version, use the latest supported distribution
$ vi ~/project/gradle-wrapper.properties ... distributionUrl=http\://services.gradle.org/distributions/gradle-1.12-all.zip
This can be set in Android Studio at Preferences | Gradle (but 0.8.7 was giving me ‘invalid location’ errors).
The 'wrapper' is just a copy of Gradle for each Android Studio project. It allows you to have Gradle 2 in your OS, and different versions in your projects. The Android Developer docs explain that here.
Then adjust your build.gradle files for the plugin. The Gradle plugin version must be compatible with the distribution/wrapper version, for the whole project. As the Tools documentation (tools.android.com/tech-docs/new-build-system/user-guide#TOC-Requirements) is slightly out of date, you can set the plugin version too low (like 0.8.0) and Android Studio will throw an error with the acceptable range for the wrapper.
Example, in build.gradle, you have this plugin:
dependencies {
classpath "com.android.tools.build:gradle:0.12.+"
}
You can try switching it to the exact version, like this:
dependencies {
classpath "com.android.tools.build:gradle:0.12.2"
}
and (after recording what version you’re changing from in each case) verifying that every build.gradle file in your project pulls in the same plugin version. Keeping the “+” should work (for 0.12.0, 0.12.1, 0.12.2, etc), but my build succeeded when I updated Google’s Volley library (originally gradle:0.8.+) and my main project (originally 0.12.+) to the fixed version: gradle:0.12.2.
Other checks
Ensure you don’t have two Android Application modules in the same Project
This may interact with the final solution (different Gradle versions, above), and cause
UNEXPECTED TOP-LEVEL EXCEPTION: com.android.dex.DexException: Multiple dex files define (various classes)
To check, Build | Make Project should not pop up a window asking what application you want to make.
Invalidate your caches
File | Invalidate Caches / Restart (stackoverflow.com/a/19223269/513413)
If step 2 doesn't work, delete ~/.gradle/ (www.wuttech.com/index.php/tag/groovy-lang-closure/)
Quit Android Studio
$ rm -rf ~/.gradle/
Start Android Studio, then sync:
Tools | Android | Sync Project with Gradle Files
Repeat this entire sequence (quit...sync) a few times before giving up.
Clean the project
Build | Clean Project
Project structure mismatch; see https://stackoverflow.com/a/64962359/8740349 for details.
If You See This...
In my recent builds, I kept seeing horrible fails (pages of exceptions) but within seconds the messages would clear, build succeeded and the app deployed. Since I could never explain it and the app worked, I never noticed that I had two Gradle plugins in my project. So I think the Gradle plugins fought each other; one crashed, the other lost its state and reported the error.
If you have time, the 1-hour video "A Gentle Introduction to Gradle" (www.youtube.com/watch?v=OFUEb7pLLXw) really helped me approach the Gradle build files, tasks, build decisions, etc.
Disclaimer
I'm learning this entire stack, on a foreign OS, after working a different career...all at the same time and under pressure. In the last few months I have hit every wall I think Android has; I've been here quite often and this is my first post. I thought this was a hard fix, so I sincerely apologize if the quality of my answer reflects the difficulty I had in getting to it.
Download system image(of targeted android level of your project) from sdk manager for the project you have imported.
This error comes when you do not have target sdk of your android project installed in sdk folder
for eg. Your imported project's target sdk level may be android-19 and on sdk folder->system-images you may have android-21 installed. so you have to download android-19 system image and other files from sdk manager or you can copy paste it if you have the system image.
Remove:
<facet type="android" name="Android">
<configuration />
</facet>
in your iml file. That works for me.
https://plus.google.com/+AlexRuiz/posts/49hP3V9GSGe
This happened to me recently when I close one Android Studio project and imported another Eclipse project. It seemed to be some bug in Android Studio where it preserves some gradle settings from previously open project and then get confused in the new project.
The solution was extremely simple: Close the project and shut down Android Studio completely, before re-opening it and then import/open the new project. Everything goes smoothly from then on.
Apparently this error has multiple causes. Here's what fixed it for me.
I was running the build command like this:
./gradlew :testapp: build
Running it without the space fixed the issue:
./gradlew :testapp:build
I got this error when switching from one Git branch to another, and then trying to run "Clean Project". I used ack to search for the Task name, and found it in a .iml file.
My solution was to regenerate the project's .iml file by clicking (in the main menu) Tools > Android > Sync Project with Gradle Files. (Thanks to this answer.)
In my case, setting the 'Gradle version' same as the 'Android Plugin version' under File->Project Structure->Project fixed the issue for me.
Simple fix for me was
Build > Clean project
Restart Android Studio
Yet another solution to the same problem:
This happened to me every time I imported an eclipse project into studio using the wizard (studio version 1.3.2).
What I found, quite by chance, was that quitting out of Android studio and then restarting studio again made the problem go away.
Frustrating, but hope this helps someone...
Sometimes, if you have opened two windows of Android Studio, and when you try to compile, this issue might happen. For me, when I was compiling a backed Google Cloud Endpoint module which was not embedded in a project, rather shared among different Android Studio projects, and when there is more than once instance open, this error use to spring up for me. But as soon as you close other windows, everything will be fine. Sometimes, you might have to restart Android Studio altogether.
I got this problem because it could not find the Android SDK path. I was missing a local.properties file with it or an ANDROID_HOME environment variable with it.
Make sure you have the latest values in your gradle files. As of this writing:
buildToolsVersion "21.1.2"
dependencies {
classpath 'com.android.tools.build:gradle:1.1.0'
}
Open Command Prompt
then go your project folder thru Command prompt
Type gradlew build and run
Apparently this issue caused by Android Studio on the various situation but the reason is build error When importing an existing project into android studio. In my case, I've imported my exist project where I was supposed to install few build tools then finally build configuration was done with error. In this case, just do the following things
Close the current project
File>New>Import Project (Don't use the open recent project)
Note:
I'm sure this kind of error is not on source code when this happened on Import project.
Problem
I specifically got the "[module_name]:prepareDebugUnitTestDependencies" task not found error, every time I ran gradle build. This happened to me after updating my Android Studio to 3.0.0.
Investigation
I had previously added command-line options to the gradle-based compiler, which you can find under: File -> Settings -> Build, Execution, Deployment -> Compiler -> Command-line Options. Specifically, I had excluded a number of tasks, including the aforementioned task. While that worked fine on the previous stable version (2.3 at that time), it seems like this was the reason behind the build failure.
Solution
This is one of many possible solutions.
Make sure you have the correct command-line options specified in the settings under: File -> Settings -> Build, Execution, Deployment -> Compiler -> Command-line Options, and that none of them is causing this problem.
In my case, I removed the exclusion of this task (and other tasks that seemed related), left the unrelated tasks excluded, and it worked!
I had the same problem and the "Tasks" tab doesn't appear to me on the Gradle settings, neither doing the commands gradlew signinReport or something.
I fix it doing the following steps:
1.- Add android: exported = "true" in my main activity of the AndroidManifest (because that Activity has an intent-filter)
2.- Update in Build.gradle (app) the compileSdkVersion to 31
3.- Update in the same place the targetSdkVersion also to 31.
4.- Click on "Sync now".
And that works for me.
Farewell!
For this you may simply just goto: SETTINGS > EXPERIMENTAL > Then uncheck the option:
"Do not build Gradle Task List during Gradle sync", Click on "Apply" > "Ok" and then click on the "Sync Project with Gradle files" option from the right side of the menu bar.
Your issue should be resolved.
Set the path of the root folder and after run the below command
ex : cd C:\Users\maha\Documents\gradle\gs-gradle-master\initial
This is what I did
Remove .idea folder
$ mv .idea .idea.bak
Import the project again
I remove/Rename .gradle folder in c:\users\Myuser\.gradle and restart Android Studio and worked for me
In my case, I meet this problem that compile options in Android Studio is "stacktrace." Modify stacktrace to --stacktrace, the problem solved.
I have solved this problem You just need to Create file in Android Folder
Go android folder
Create file local.properties
then just add this code in local.properties file:-
If you are using MacBook then sdk.dir=/Users/USERNAME/Library/android/sdk
if you are using Windows then sdk.dir=C:\Users\USERNAME\AppData\Local\Android\sdk
if you are using Linux then sdk.dir = /home/USERNAME/Android/sdk
if you want to know what is your system USERNAME then just use command for Mac whoami
and then just rerun command react-native run-android
Thanks :)
Am on Mac so answer is as per like that.
Go to Android Studio(From Menu Bar) -> Preferences -> Build, Execution, Deployment -> Compiler . Then look for Command-Line Options , there make sure nothing typed in its Text Field. That should be empty. Then rebulid project and thats it.

Gradle Sync wont finish after 0.4.6 upgrade

After I upgraded my Android Studio to 0.4.6, it seems to get stuck with Gradle Sync. The yellow ribbon is persistently present on the top that says "Gradle Project Synch in Progress". However, there is no indication of any process running from the bar at the bottom.
When I try to run my application, it fails with "Gradle Project Sync Failed. Please fix your project and try again" message that appears in a balloon. However, there are no more information.
I was working on this project successfully before I upgraded to 0.4.6. And since 0.4.6 was updated quickly (within 5 days) from 0.4.5 to fix some gradle related bug, I am starting to wonder if this is something new they introduced.
I just encountered the same problem this afternoon. I'm running on IntelliJ IDEA, should be similar.
What I did is:
remove local Gradle from the $PATH (I used to set GRADLE_HOME variable and it's a different version)
in build.gradle, change the classpath to
classpath 'com.android.tools.build:gradle:0.10.+'
click File > Invalidate Caches/Restart (you can also manually remove the cache at ~/Library/Caches/{yourIDEName} and restart the IDE)
After this, the "Gradle Project Sync in Progress..." disappear once completed the syncing and I'm able to run my project again.
I had a similar issue:
sync message stuck
can't build/rebuild (failed to sync message)
settings.gradle file is empty - has content with external editor.
I've downloaded a cannery version 0.8.11 (problematic version 0.8.9) which fixed the issue (after reverting settings.gradle to the version control revision).
Had the same problem
Was messing with .gradle code and removed include ':app' from settings.gradle on accident

Specifying Maven dependencies in build.gradle doesn't work

I tried to add a Maven dependency to my project, which uses Gradle, by adding these lines to the build.gradle file in Android Studio:
repositories {
mavenCentral()
}
dependencies {
compile files('libs/android-support-v4.jar')
compile 'org.roboguice:roboguice:2.0'
}
The project seems to compile well, but there's no way to reference Roboguice classes inside my project's code. I feel like I'm missing something, namely, how does Gradle download the dependency and where will it store it? How should I fix my project?
Using the command line, in the root of your project, run :
./gradlew clean && ./gradlew build
Then recompile your project in studio and you should see your new dependencies.
EDIT: At the time of the answer, Android studio didn't propose the "Gradle sync" button. It now does, so rather than using the command line, you can hit the button, and it will basically run ./gradlew clean && ./gradlew build for you.
Anyway, it's always good to know how to do it in command line :)
The name of the button is: Sync Project with Gradle Files
See the screenshot below.
On Android Studio I just press the Sync Project with Gradle File button, left of the AVD Manager did the job. No restart, no ./gradlew clean or ./gradlew build.
You can also navigate through Tools-->Android-->Sync Project with Gradle File.
I was having the same problem. I tried all solutions suggested without success. Then I simply closed and opened again Android Studio and it worked!
Nothing here worked for me. What did work was File -> Invalidate Caches / Restart...
This is an extremely annoying bug, that happens way more often that it should. The build tools should not be a hindrance to development.
go to intellij preferences and enable gradle auto import dependencies

Categories

Resources