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.
Related
I am trying to rebuild an old (working) project in AndroidStudio. It builds Ok but strangely, the project's build.gradle is not visible in the AS Project tab.
Note that the module's build.gradle appears but not the project's build.gradle.
Both files ARE indeed there
Directory of C:\dev\AndroidProjects\apps\Passwords\app
11/09/2020 04:16 PM 767 build.gradle
1 File(s) 767 bytes
Directory of C:\dev\AndroidProjects\apps\Passwords
11/09/2020 03:13 PM 352 build.gradle
1 File(s) 352 bytes
The project otherwise builds just fine.
The projects build.gradle IS active: If I make changes to it outside AS using a text editor, the changes DO take effect.
What I've Tried:
Restart PC and AS
Cleaned/Rebuilt Project
Invalidate Caches & Restart
Searched SO for problem. Question 47406517 was similar but solution didn't work
Copy build.gradle from another known-good project.
Notes:
Android Studio: V3.6.3
PC: Win10-64
Project Name: "Passwords"
I'm at a loss for other things to try. Any suggestions?
(I guess as a work-around, I can always use an external text editor but that's annoying).
I found the answer in SO question #46230078. The solution was simple: Close AndroidStudio, delete the directory ".idea" from the project directory, restart AndroidStudio. This did it!
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 am having an issue to configure Android studio after importing gradle project. My project structures is as following:
Root Project
|_.config
|_settings.gradle
|_build.gradle
|_app_module
|_lib1_module
|_lib2_module
|_ etc.
Please note, that for several reasons I am not able to move settings.gradle and build.gradle files to project root . Also, the files mentioned above are configured correctly, so there is no problem with the build.
So the problem is that once the project in imported, the all gradle related file and folders are are generated inside .config folder, which doesn't disturd me.
Also the .idea folder and all relevant sub-folders are generated in this very folder.
So this is the problem. For some reason, the studio doesn't recognize all sub-modules are under source control. I.e. it's vcs.xml is empty and contains only project root. Actually the problem is resolved by adding the modules via settings--> subversion menu, but I'd really like out-of-the-box solution. I've tried to put .idea folder under source-control - doesn't help. Upon project creation, the vcs.xml is re-written and empty again.
So, the main question is:
Is there a possibility to
Force studio to generate .idea folder and the root project folder without changing location of .gradle files OR
Make studio NOT to re-write it's settings files upon project import (e.g. keep predefined vcs.xml)
PS. I'm aware the putting all generated files (including gradle folder, gradlew, etc.) will probably solve the issue, but I wouldn't like to go so far.
Thank all in advance
It should be a comment, but it is too long.
Android Studio works with a project.
Inside this project you can configure more modules but it need this structure:
Root Project
|_.idea
|_.gradle
|_.config
|_build.gradle
|_app_module
|_build.gradle
|_lib1_module
|_build.gradle
|_lib2_module
|_build.gradle
|_ etc.
|_settings.gradle
|_build.gradle
Inside the settings.gradle you have to define all modules:
include ':config' , ':app_module' , ':lib1_module', ':lib2_module'
Under the root folder, Android Studio when builds the project with gradle, makes same folders, like the .idea.
I read that your are not able to move the settings.gradle file.
In this case Android Studio recognizes the config folder as the root of a project and build the .idea folder inside.
|_.config (root)
|_.idea
|_.gradle
|_build.gradle
|_settings.gradle
|_myModule
Force studio to generate .idea folder and the root project folder without changing location of .gradle files OR
As I know you can't avoid this.
Also ,
Make studio NOT to re-write it's settings files upon project import
The .idea, the .gradle folder, the .iml files are built locally by the IDE when the project is built. The IDE re-writes these resources, also these files contain local paths and usually they are not commited in VCS for this reason.
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.