Im using Back Track r3 and android studio 0.8.6, every time i start a project i get
"Gradle project refresh failed - cause error in opening zip file"
error message, what can i do to fix it?
update:
after trying to delete /gradle folder in plugins
this is what i get.
only more errors i cant rebuild the project
Delete everything in the .gradle directory in your home directory, and also the .gradle directory in your project, and rebuild.
The rebuild will take some time because it will need to re-download a bunch of Gradle and project dependencies, but I think one of those has become corrupted.
Old, but had it today on a react native generated project :
so I deleted the content of the gradle dir at the root (myproject-dir/android/gradle) of the android project -> it redownloaded everything, and it was fine !
Hope this will help someone.
Related
I am beginner in developing test automation for Mobile apps, and already I am facing "Cannot resolve symbol........." issues. I have also done a "sync to Gradle".
I have a MainActivityTest class which consist of the following :
As can be seen, the red-colored texts are giving me the issues of "Cannot resolve symbol when mouse-over them.
The following is the Gradle in my app module
Hope to have advice as what have I done wrong.
Steps you can explore:
Step 1: File > Sync Project with Gradle Files.
Step 2: If it doesn't work even now, File > Invalidate Caches and Restart.
Step 3: After you restart, you can Clean Project, Rebuild Project.
Another Step: File > Close Project, and reopen it.
Edit:
If you didn't find any solution to the problem with the above steps you can follow the following steps.
Close Android Studio.
Let Us consider your project name is ' AndroidProject '.
Go to your project folder (...../AndroidProject/). It will have app/, build/, gradle/, release/ folders and build.gradle, gradlew, gradle.properties, 'gradle.bat, settings.gradle, local.properties` files.
Delete the build/ folder. (Don't worry nothing is going to happen! This folder is something that is generated).
Now navigate into app/, and delete the build/ folder in that as well.
Open Android studio now. The project will rebuild. Your errors will be gone.
I have converted one of our Android projects from the old Groovy settings.gradle and build.gradle files to the new Kotlin DSL, i. e. settings.gradle.kts and build.gradle.kts.
While "it works on my machine" - in particular: the original project I converted from Groovy to Kotlin works fine in its original directory - all my co-workers are unable to open the project when they clone the repo. Importantly, neither can I open the project myself (with the same AS installation on the same machine) when I clone the repo to some other directory. So, I suspect there is some additional detail missing in some configuration file but I cannot seem to figure out which...
Details:
When I just use File > Open... and then select the project folder, I only get the error message "The project 'xxx' is not a Gradle-based project"
When I instead go through Import Project (Gradle, Eclipse ADT, etc.) and then select Import project from external model and Android Gradle Android Studio will create an empty build.gradle file and fail with the error message "ERROR: Plugin with id 'com.android.library' not found." Deleting the build.gradle just goes back to the error message I described in the first bullet point.
I am aware of this Github issue, which seems to describe the same problem, but it's been very quiet and I thought someone around here must have figured out a solution to this...
Oh, command line builds work everywhere - this is purely an Android Studio problem.
UPDATE: When I copy the whole project to a new folder (instead of cloning the repository) I can open it without any problems. So, am I correct in assuming that there must be something inside the folder - but not in Git - that makes it work?
I was able to 'fix' it by deleting the .idea directory and reopening the project. The .idea directory is usually not committed in git but I guess copying the directory invalidates the directory structures in the files within the .idea directory.
The whole bug is easily reproducible when you click on File > Re-import Gradle project.
#Boni2k answer does not work for me.
I have to rename the root build.gradle.kts back to build.gradle, fix the syntax error, sync the project (which works fine immediately), and rename the file back to build.gradle.kts. Then the error is gone and I can sync the project successfully.
What I did to raise the error was that I moved the project to a different folder, and rename the project.
I had the build/make error
Error:null value in entry: resOutputDir=null
when building my project in AdroidStudio
The solution was to simply delete the .gradle folder in the root directory. (backup to make sure you don't blow something up).
answer found here: https://discuss.gradle.org/t/null-value-in-entry-dependencycachedir-null/19191/3
I have solved this and other Gradle build errors by executing the menu sequence: "Build > Clean Project".
I stuck in the problem like this. What I done is; Delete the .Gradle Folder From the Project File in the Project location.
Then Built and Clean the Project. I searched a lot on Google but the Solution I got from a blog is...
Delete .Gradle Folder -> Clean->Built
In my case I had a typo in the variable. domain instead of Domain.
In Android Studio, I wanted to rename the root directory. There was no way to do this within Android Studio, so I exited AS and renamed the folder and then opened the project again. But when I went to run the app, it indicates:
AndroidManifest.xm does not exist or has incorrect root tag
The manifest does exist, but apparently something breaks by renaming the file. I tried invalidating the cache but that didn't help.
Closing the project and then removing it from the list and then reimporting the project as a non-Android project corrected the problem. Still, this seems to be a hack. It should be possible to rename the root folder without having to take this approach.
i use ActionBarLibrary in a library, that I use in a my app
i got this message when i try to compil
[2013-01-28 16:09:46 - Dex Loader] Unable to execute dex: Multiple dex files define Lcom/actionbarsherlock/R$attr;
[2013-01-28 16:09:46 - comfree] Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define Lcom/actionbarsherlock/R$attr;
As asked here, I was facing the exact same error yesterday. I pinpointed the cause of the error to /bin/classes. If I deleted the /classes dir before running the app, the app would compile and run. Of course, when I tried to actually export the app, the /classes dir would come back and along with it the error.
The solution to my problem was to install the latest version of Eclipse. You will then need to install the latest version of the ADT but all the Android versions you have downloaded earlier for the other Eclipse installation will be detected and used for this one as well. When I export or run the app through Eclipse, the /classes folder does not appear now.
right click on project to go project property>>java Build path>>choose Order and Export and then Unselect all except android4.0 or what every you have then clean and build your project ,now error not come again..
The solution to my problem was that I deleted the jar files which I copy pasted in project's lib folder. I explicitly imported external jars in build path