I just installed Eclipse on my Mac, I downloaded the bundle that provides Eclipse+SDK, I've also downloaded all the needed updates but when I create a new project I get the following error:
[2014-08-25 16:51:02 - provaApp] Project has no project.properties
file! Edit the project properties to set one.
I've tried everything found here on SO but none of the answers worked, I really have no idea on how to fix this. I've also deleted and downloaded Eclipse twice.
Edit: I get also the following error if I try to edit the properties of the Project by right-clicking on Project Root folder > properties > Android
If I try to set the project build target (in my case Android 4.4W) I can't because it doesn't save the changes.
What I know works is if you create a new blank project, copy that project.properties file into the existing project and it should work. Also try running a clean project sometimes helps, but very rarely.
It's a pain but luckily this happens rarely.
Try to create a project.properties file with this content:
target=android-19
Related
a few days ago i have lost my R.java file from my android app app project from android adt while cleaning it...as it was showing some errors when i was trying to add the feature of ads in my xml file...now i am unable to recover my R.java file in the project .
I have tried many options such as:-
cleaning the project .
checking for errors in the xml file and corrected and tried to clean the project once again.
copied and pasted the res,gen and android manifest.xml file in the new project of the same in another workspace and pasting the new R.java file generated over there into the actual workspace but still its not working and showing errors.
i tried to cut and paste the sdkmanager.exe from the actual folder to some folder elsewhere and tried to clean the project again to regain its R.java file but it is still not working and the sdk manager is showing the same path even though i have shifted it somewhere else...
now what am i supposed to do...
To change SDK path: Window/Preferences/Android.. and then Set SDK Location
R.java is an auto generated file and it's error is based on errors in Manifest file or resources , maybe there is an unnamed string in your string file ,if you can, post your R.java file errors. and for changing sdk path its through Window -> Preferences - > Android .
On Windows : Window > Preferences > Android. Then click on "Browse" to change SDK path.
On Mac : ADT > Preferences > Android and "Browse"
You need to provide your R.java file errors mine was R cannot be resolved to a variable and I had to go to project properties -> java build path, then make sure your libraries are selected and clean and build and if that doesn't work delete your bin and gen folder and clean and build...Hope this works for you good luck!
I got this error on Android Studio (AS):
How I got it:
I created an AS Project from scratch and everything was fine.
Then a popup showed up, and (if I recall correctly) was saying something like: "Android Framework detected". I pressed "Yes' and some changes happened to the project/module. And after that I got the above error
Edit:
In my case the problem was not Gradle related. It had to do with IntelliJ/Android Studio configuration, an .iml file in particular.
I realized that after reading this informative post here.
On Android Studio v0.8.2 clicking on Sync project with Gradle files button solved my problem.
update
Thanks to the comment of jaumard. If the Sync project with Gradle files it's not visible you have to open the Gradle panel and click sync icon on top the toolbar.
Just call (in any case) File -> Invalidate Caches and Restart....
In my case:
settings.gradle file was empty. I added defualt code:
include ':app'
Then I clicked
Then project start works.
Double check that under project structure / module / Manifest file it points to the correct manifest file in your code and not the one in generated sources.
This is true for both Android Studio and Intelli J. Sometime when you import project from existing sources it prefer the manifest file inside the generates sources directory.
What helped for me was:
delete .gradle/ folder
delete .idea/ folder
delete ****.idea*** file
reopen Android Studio
import from gradle as Android Studio then suggests
I ran into a similar problem. Looks like my .../src directory for whatever reason moved under my .../lib directory. I moved it out of the /lib directory. Now both /lib and /src are at the same level. After a couple of clean rebuilds and restarts of Android studio everything is back to normal. My emulator started up fine.
You might want to check your directory structure. Compare the directory structure with a working project. You might be able to see the difference.
Moving my AndroidManifest.xml to PROJECT_NAME/src/main fixed the issue.
I had the same errormessage and noticed I had 2 MYPROJECTNAME.iml files, but with a different casing of MYPROJECTNAME. I created this situation after checking out from SVN the project into a directory with the casing error.
Just throw away the IML file with the wrong casing, after saving the content of both and use the content that works
I had this problem with a multi-module project when I renamed the app module. In my case to solve the problem I had to manually update the app module name in the project's settings.gradle file (Android Studio didn't update that value)
Happened to me. Found that i had wrongly opened the parent folder of the actual project in Android Studio.
In my case, it was my AndroidManifest.xml file, it was all messed up due to a new library that I added in my build.gradle.
So I took the AndroidManifest.xml from my latest commit on Git and I replaced it the current one, and also my settings.gradle was empty so I added include ':app'.
Hope it helps, and happy coding !
Facing same issue, resolve after adding the missing build.gradle file in root project.
I'm using git, and creating lots of git branches for new features on a project I'm working on. Every once in a while, I'll create a new branch off master as usual (let's call this broken-branch, and this error appears:
Android Source Generator: [demo] AndroidManifest.xml file not found
I'll create a new branch off master, cherrypick the changes on broken-branch onto this one, and everything works fine. Why do I get this error, and how can I avoid it?
This happened to me today.. I clicked "Sync Project with Gradle Files" and all went fine.
While my IDE is IDEA13 with maven. Work fine with maven in command line, while using IDEA run( shift + F10) show this error. I do as below and fix this:
1.Open .iml in the project root.
2.Find some line like:
<option name="USE_CUSTOM_COMPILER_MANIFEST" value="true" />
3.Remove this line or change value to false.
This is my work way.
May Help.
I use IntelliJ Idea and found next solution:
in the root of the project (in catalog with root build.gradle) create file settings.gradle which consist include ':app'
Than go to IDE and run Gradle - refresh.
I know the problem in IDEA because you create a new project with Java configuration (not android, but with android sdk dependency)
File > New Project > Java (Java Module) > Project SDK Android 4.X
Here is the solution :
File > New Project > Android (Application Module)
If you are using Maven, backup the project and close it. Open IntelliJ and select Open..., choose the pom.xml file and then select yes to open this project. Because there is already a project a popup should appear, choose 'Delete Existing Project and Import'.
Note: I'm using IntelliJ Community Edition version 13
When I get "AndroidManifest.xml file not found" error I clean and then refresh the project and these steps seem to fix the problem.
It happens to me when I don't have .iml file to open the project. It's very easy to fix, you just need to close the project and reopen it taking care of select build.gradle file before click open.
I hope it helps somebody.
This worked for me.
My project already had a settings.gradle file.
I simple had to add the line include ':app' . N ow i can build and do everything.
open IDE
project
|--->build automatically
uncheck it
clean the project
check build automatically opriot
I just had this problem while trying to build the swagger code gen project. For whatever reason IntelliJ thought I should have an Android facet. Removing this facet allowed the entire project to build.
If in case, you encounter an error which shows:
AndroidManifest.xml file is not found
All that you have to do is reinstall the flutter package and the error is resolved!!!
Go File,Project Structure or press Ctrl+Shift+Alt+S,
Go Facets, Select your android project, in the structure there are configuration files, folders. Image of structure tab (before)
Location of AndroidManifest file was like this:
D:\Programming\Dart Flutter Projects\tip_calculator\AndroidManifest.xml
Change the location like this.
Image of structure tab (after)
Changed it to here:
D:\Programming\Dart Flutter Projects\tip_calculator\android\app\src\profile\AndroidManifest.xml
flutter upgrade --force
Helped me.
Works for you?
So I started a new android project in my default workspace. Then I decided to copy the project to another folder and imported the android project. Now when I start Eclipse, I switch the workspace to point to this new folder.
What I'm experimenting now is that eclipse seem no longer to regenerate the R.java values. Also the designer of my layout doesn't display the designer at all .....
How can I fix this?
Do the following ...
1: default.properties or project.properties is present in your project?
if project.properties is present then rename to default.properties
2: Clean your project and restart your eclips.
Hope this will helps you...Enjoy
clean the project when ever you are copy project, some time r.java not genrate so you need to clean project. so it will generate properly.
I have an Android project developed on Eclipse (GNU/Linux) that I last touched half a year ago. I am trying to import the project into Eclipse 3.6 on Windows (with ADT installed) installed using File -> Import Project in Eclipse. When the project is imported, I see the following error twice on the console:
[2010-12-10 02:17:12 -
com.android.ide.eclipse.adt.internal.project.AndroidManifestHelper]
Unable to read C:\Program
Files\Android\android-sdk-windows\AndroidManifest.xml:
java.io.FileNotFoundException:
C:\Program
Files\Android\android-sdk-windows\AndroidManifest.xml
(The system cannot find the file
specified)
Why is Eclipse looking for AndroidManifest.xml on the Android SDK path? The file actually seems to be in the project's directory. How do I fix this problem and get the project to compile?
A simple solution is to either reimport the AndroidManifest.xml file or make a change to the file and save it. This worked for me.
If you see an error about AndroidManifest.xml, or some problems
related to an Android zip file, right click on the project and select
Android Tools > Fix Project Properties. (The project is looking in the
wrong location for the library file, this will fix it for you.)
from: http://developer.android.com/resources/tutorials/notepad/notepad-ex1.html
The way you are importing the Android project into Eclipse is wrong. The Correct way of doing is File -> New Android Project. In the Contents Tab in "New Android Project", select "Create project from existing source" and choose the Build Target. That should fix your problem.
It appears that this error is produced because Eclipse thinks the default location for new Android projects is the Android SDK path. Even if the project location is changed, the error fails to be resolved, so the trick is to change the project location before Eclipse is aware of the condition generating the error.
To circumvent this quirk I imported the old project with the following steps:
File -> New -> Android Project
Un-check 'Use default location' and browse to project root directory.
Click 'Create project from existing source'
It's important to do step (2) before (3) otherwise the error persists and prevents running the project.
I had the same problem, all of the above did not work. I cleaned the project and it worked.
Instead of using File ---> New Android Project --> "Create project from existing sources", which will result in the error your are seeing, choose "Create project from existing sample" and choose it from the drop down. This will work.
Experienced JAVA developers tend to go with the first option which is normally there and works for classic Eclipse projects. But this is not your typical project and I bet the Google developers put this special case in the wizard to accommodate the differences.
I had the same problem. I was trying to compile the JakeWharton view page sample, so I checked out the GIT in a directory in a different folder then the workspace which caused the problem.
Eclipse was maintaining 2 folders:
1. A new workspace folder was made under the workspace directory, which eclipse checks for libraries and others source code including the AndroidManifest.xml file
2. The existing folder which was not under the Root workspace
To fix the problem after importing I had to manually move the files in the new workspace folder created by eclipse.
I met this problem when using Facebook SDK, now I solve it by doing this:
Close the project;
Copy "AndroidManifest.xml" file to the project's root path;
Open the project and refresh it, it's Done!
this worked for me by the way:
I changed the project name to the exact name of the project that I am importing.
Eclipse seems somewhat fragile in its naming conventions. One of the causes for this error is a difference between the project name and the folder name in the workspace. I imported a zip file for a project named "HelloDialogs" into a workspace folder named "HelloDialog". This caused the "AndroidManifest.xml file missing" error. Once I renamed the folder correctly, everything worked fine.
Because of the multiple different answers here, I thouhgt I'd add yet another one that worked for me, as I had exactly the same issue when first working with Phonegap android dev tools.
So I found (as mentioned by Gintautas in comments to the accepted answer), that I had to create a new project using the phonegap 'create' script, then when importing the project into eclipse. the only way to get this to work successfully was if the project was originally created in some temp folder somewhere other than the place I actually want to work with it.
So I created a project in windows like this in a cmd window...
c:\phonegap\phonegap-2.6.0\lib\android\bin>create.bat c:\temp\android_boilerplates\test app.test test
Then I imported the project in eclipse like this...
File > New > Project
Within the new project wizard select: "Android Project from Existing Code"
Click "Next"
Now navigate to the temp location of your project and set that to the root directory, check the project you want and check "Copy projects into workspace" as the example below...
Click "Finish"
And that's it, Eclipse should copy all your project files into your workspace and there shouldn't be any errors in your project (fingers crossed).
Your project should look something like this...
Hope that helps, it took me an age to work out why Eclipse didn't like creating a new project from existing code when the new project was being setup in the same place as the existing code. This isn't a problem for other languages I've used, so it was a little weird, but understandable as Eclipse (I'm guessing) seems to want to overwrite certain files.
Eclipse randomly decided to make another folder instead of the one that i had specified, but doesnt have any resources or data or layout etc in it..
it has some conflicts i guess..
anyway, a noob approach to this was, copying the original file to some other location(i put it to desktop)..
now create new project-create existing project, select this one from desktop, n VOILA.. its all fine.. :D
I am a little late to this game but I caused this same problem by generating the initial application into the exact location I was going to work on it. That is to say I put it directly into my current workspace. I then did File, Import, Existing Android Code Into Workspace. The import process blanked out my android.xml file.
I tried above solutions and had no joy. I then generated the initial application into a temp directory and imported from there. This worked for me.
The only way to import a project into eclipse workspace is to create an empty project and then drag and drop all the folders and files into this project. Why is this so is beyond me.
The answer from Raunak is wrong.
I found a .classpath file in the root directory of my Android project. I opened it and updated the file paths in it, and it seemed to fix the problem for me.
I had the problem when I tried to update an old project with recent code from the SVN. I had the Manifest.xml exported to my local file system as backup and deleted it. I've then reverted my complete project to the most recent version from the SVN and then it worked :)
This is what I had to do to get this to work. Fortunately I had backups of earlier "project".
1) Import the project as usual.
2) If the errors with empty xml etc. comes up, close the project.
3) Go to the original project if you have backup.
4) Copy all of the projects root files and directories and paste it over where Eclipse expects the projects root directories and files to be.
5) Open the project and refresh. Make "Clean" if necessary and you're done!
Always make backups because Eclipse f--kups! I learned this the hard way when suddenly my Android project refused to work because of empty manifest-file.
Sometimes if you automatically fix imports in MainActivity IDE imports android.R class instead of one that will be generated for the project. Remove the import and recompile.
when importing project from another workspace add existing project in workspace. and tick to the copy projects in workspace.then check the api level and supporting library from project.properties files.then rebuilt project and clean it.. it is works for me.
2017 Solution: Much Easier and tested solution is to remove your application folder from elipse project only then Import it again and the problem will be fixed immediately!