While creating an android project in Eclipse, I get the error:
[2014-03-13 15:14:36 - appcompat_v7] WARNING: unable to write jarlist cache file C:\Users\Neelakanteshwar\AndroidFirst\appcompat_v7\bin\jarlist.cache
And appcompat_v7 folder is created along with project folder in Eclipse.
Can anyone please help me to get the solution.
If you go to appcompat_v7/bin folder, you'll see that file jarlist.cache doesn´t appear or is unsynchronized. You need to refresh the appcompat_v7 folder, only press F5 over that folder.
The appcompat_v7 folder is added because you use an action bar component.
Aah. To avoid a new appcompat_v7_XX folder when you are creating a new project, choose a LEVEL API 14 as Minimum Required SDK.
After that, you must modifier the AndroidManifest.xml and put the level that you need.
<uses-sdk
android:minSdkVersion="14" ------> change it
android:targetSdkVersion="19" />`
Heads up! Delete all appcompat_v7_XX. It is a bug.
With appcompat_v7, you will see that Eclipse creates two XML files:
activity_main.xml
fragment_main.xml
If you want to have an option to create a project in the old way only with activity_main.xml, do that:
Make a copy of the folder "BlanckActivity" located in this path: \sdk\tools\templates\activities of an ADT previous version.
Rename the folder as BlankActivityNoFragment, then edit the field name of the file template.xml such that, it reads name=BlankActivityNoFragment
Copy the new folder in the same path of the new Eclipse IDE: sdk/tools/templates/activities
Now you´ll see the new template when you go to create a new project.
Remember to choose as Minimum Required SDK as API 14
Also got the same problem today.
Install and configure all the required components.
On the menu bar, go to: Project->Properties->Java build path.
On the order and export tab: check all the project libraries. I checked Android 4.4.
Change Workspace path in starting Eclipse:
from C:\Users\XXXXXXXX\workspace
to, for example D:\My_Folder
This may not be the professional way but it worked for me.
Manually create a folder named jar in the path: C:\Users\\***\appcompat_v7\bin\
Referesh your project in eclipse.
That's because you also need Adroid Version 2.1!
Go to Android SDK Manager and download Android Version 2.1 (API 7)
If you start a new Android App. Project there is typed that FROM 2.1 TILL 4.4 Android version.
So that mean the program is searching for the minimum Android version bro :)
BTW: Download the 2.2. Android Version, too. :)
Just got the same problem today.
In my case the combination of your advices became a solution:
In Eclipse project bar I have deleted Appcompat(XYZ) and the new project that I just created.
Checked for updates - no updates were found.
Clicked File -> Restart.
While creating new project have chosen API 14 as Minimum Required SDK.
Done.
Run an Eclipse update (Help -> Check for Updates) and let me know if this resolves your problems.
Just refresh the bin folder of appcompat_v7!
This worked for me.
When create android-support-v7-appcompat, mark the option "Copy projects into workspace". Now, it can write in the required directories.
I hope this is helpful for you.
Well... I met the same situation. I deleted my project from eclipse and on the disk, delete the workspace from the disk, and recreate the project in the new workspace... it works.......
A different approach worked in my case, saying it here if it can help someone. I also came across this weird problem of appcompat while creating a new project.
I have just clean and build the default appcompat_v7 project for 2 times which is created by eclipse itself and voila it worked! and all errors are gone, works perfectly.
I got the same error and the following steps worked for me.
Just delete the gen and bin folders
Clean(Re build) the project.
Here is *Simple Trick:*
Create New Project
If you get the warning of jarlist Not created under the console tab
Close Eclipse and ReOpen it
Now u r done. jarlist is included in appcompat_7/bin or appcompat_7_XX/bin
Related
I have just imported my eclipse project in android studio. it keeps my saying that
Error:SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.
I have seen some tutorials of editing local.properties files but it didnt work. here is my project.properties file:
sdk.dir=E:\\Mod Eclipse\\adt-bundle-windows-x86_64-20130219\\sdk
Actual directory of my folder is :
E:\Mod Eclipse\adt-bundle-windows-x86_64-20130219\sdk
A quick note about this if trying to run a Facebook sample and this error pops up, make sure you select the build.gradle file in the root of Facebook sdk, for all the samples when 'opening an existing project'. I got this error when I tried to open the gradle for just the Scrumptious sample from the 3.22 SDK
If you are sure that you have assigned correct SDK path in project settings,
and you can see it in local.properties as well, but still getting this error then there are chances that you are missing something in you project.
I was getting the same error after looking in to my project I found settings.gradle was missing.
and then add following script to your apps build.gradle
You will not face this error any more. It worked for me may be gradle set up was the blocking issue
My problem was:
I cloned a project from github
I clicked open existing Android Studio project
I chose the path of the inner sample app instead of the containing folder.
So what you should do is:
close the project.
click open existing Android Studio project
select the parent folder instead of the sample app.
You should also change it on Project Structure.
Close the current project and you'll see pop up with dialog which will then proceed to Configure option.
Configure -> Project Defaults -> Project Structure -> SDKs on left column -> Android SDK Home Path -> give the exact path as you did on local.properties and select Valid Target.
There you go.
The simplest solution sometimes is just do the File -> Invalidate Cache / Restart.
If it does not help then go for the more complicated stuff, as suggested in other answers
You can add a local.properties with to set the sdk.dir like sdk.dir=/Users/roofe/Library/Android/sdk.
But please note below, which is very important,
add the local.properties to the uppermost path of the project. Here the uppermost have some difference with root path of a project.
For example in the below project, I just use the ijkplayer-example, but this module also used other module with different cpu architecture.
If I only add local.properties to ijkplayer-example will not work. Here will get sdk location issue for other module.
While I can add the local.properties to the ijkplayer directory, then when I try to open the ijkplayer-example project, there will auto create a local.properties for ijkplayer-example, and everything works well.
In my case, it was a fresh install with checkout from github.
Just close the checkout window.
Create a new project (not from git, just a fresh one).
exit the project.
checkout whatever you like
Its just the fastest way that I found.
So I had the same issue, and none of the answers given previously helped me. What I did was check for new API updates (in my case, I updated to API level 23) and the problem was fixed.
Sync project with Gradle files, It will modify the project's local.properties file.
In Android Studio, I just clicked on File and then Choose Project Structure or Ctrl-Alt-Shift+S. This'll clearly show you the Android SDK location and an input box where you can browse to the correct one if it is not correct.
I add just local.properties file where my project is located. In local.properties:
sdk.dir=C\:\\Users\\dglig\\AppData\\Local\\Android\\Sdk
such kind of path is there which is our Sdk path.
So just create local.properties file manually and inside this just copy the Sdk file location.
Probably local.properties file missing.
Copy a local.properties from an existing file and add it to your current project. That worked for me.
I installed the SDK again (from here for example :
https://www.mediafire.com/file/azbsqg6dmg7z7np/Sdk+tools+for+android+studio.rar/file
& it created the directory & the packages, after installation.
Now I open android studio & everything is normal.
Everything posted so far was helpful in an overall learning capacity. However, most of the time, fixing one problem created others. What ended up working for me was completely deleting the GitHub project .zip file and any unzipped files. Then I made sure the correct .zip file was re-downloaded and unzipped. When it came time to open it in Android studio, I noticed there were 2 folders with identical project file names, one being contained in the other. The first (or upper) one is actually the .zip file. Open the other one!
I am using Eclipse to develop Android apps. I am importing one example to the Eclipse Workspace. But I am not able to run that project as it does not load the Android library to that project.
Please see this screen shot:
In SlidingDrawer there is Android 2.2 library is added but in SlidingDrawer_Original i am not able to load the android library.
I have cleaned the project and also built the workspace but still the problem is not solved.
if I open the Java file from the SlidingDrawer_Original then it seems like below image:
So What should I have to do to load the Android Library ?
Right click Project properties >Select Android > Select your target AVD
There will be a file called .classpath , just check the Attribute of this file, It must be in read only mode, Change it to Archive Mode and the Clean the Project and set Proper Project Build and try again.
I dont know why it is Happen, But as i come to know, Eclipse always required its properties file. In Some Eclipse it is named as default.properties and in some eclipse it is as project.properties.
I have simply copy paste the default.Properties file and put it in to that project.
Then create the copy of that project in the same Workspace and remove the previous one project.
It solve my Issue. Hope it will also helpful to you.
Enjoy. :)
In order to implement different versions of our UI we broke our program up into UI specific code and a common library project that has everything else. Up until yesterday when I updated to ADT 14 everything was working fine. Now I can't build. I keep getting the error "The container 'Library Projects' references non existing library 'path to the bin folder of my common project and the name of the project.jar'
I've been all over the web and tried everything I can think of to fix this to no avail. Can someone help me out? I'm basically stuck at this point.
Maybe you have the same issues I had when switching to the new ADT:
In my previous setup I had some resources split between the library and the main project. The library project would not compile error free on its own but only in combination with the main project which added the missing resources.
It doesn't work like this any more.
The library project must compile completely error free now. When it does the build process will create a <lib_project_name>.jar in the bin folder of the library project.
If the jar file is not created ( thus the build process of the library project failed for some reason - eg. because the changes in the R.java file (see http://tools.android.com/recent/buildchangesinrevision14 )) you will get the error message you described.
Also, I had to manually remove the <lib_project>_src from the project.
I've had a problem with a few different projects where I did the fixes suggested in the other answer, but they were only fixed temporarily.
Every time I reopened Eclipse or did a Clean on a project, the "Library Projects" directory would disappear, and I would have to open the project properties, remove the library, and add it again.
I solved this the hard way by creating a new project and copying everything into it.
Then I found an easy way to solve it. Right click the project, Refactor-->Rename. You can rename it back afterwards. This fixed it.
Check out the article "Changes to Library Projects in Android SDK Tools, r14" ( http://android-developers.blogspot.com/2011/10/changes-to-library-projects-in-android.html ) on the Android Developers blog.
E.g. #P.Melch: "I had to manually remove the _src from the project" should be done as follows:
To fix the project, you must remove the extraneous source folders with the following steps:
Right click source folder and choose Build Path > Remove from Build
path.
A dialog will pop up. In it, make sure to check “Also unlink the folder from the project” to completely remove the folder.
You have to update the Android SDK in Android SDK Manager
Android SDK Tools Intalled
Android SDK Plataforms Installed
Android SDK Builds Installed
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!
I just reformatted my computer. I have windows xp sp3 32 bit.
I install java jdk
android sdk
eclipse ide
When I go to make a new android project i get this error.
Project 'HelloAndroid2' is missing required source folder: 'gen'
Please help i'm new to eclipse so give detail responses.
I just got this problem when I was trying to import a project that was originally created with a version of the SDK that is no longer installed on my machine.
Right click the project. Select Properties. Go to Android. Select a Project Build Target. Click Ok. You might have to clean and rebuild the project as well.
Right-click on the "gen" folder in Eclipse and select Properties. Then, remove the "Derived" checkbox. Then clean the project.
Most likely, there is a problem with one of your resources, preventing R.java from being generated in the gen/ folder. You should have error messages in your Console related to this problem.
Delete the "gen" folder. Then clean the project. Then build the project again. In my case it worked.
try this...
Right click on the project in eclips
Android tools -> Fix project properties
its works for me
ok , here's what worked for me:
delete the project and make sure you are not deleting it from the disk!
import it again and it will solve the problem.
Good luck....
My case was: I imported Zhou Weikan's cocos2d-android and the error emerged. The most straight-forward solution that came to my mind was to create the folder (right-click on the project in Package Explorer -> New -> Folder and then create new folder named 'gen'. It worked in my case.
delete the gen and its content and clean the project again.
Go to project
Right Click
New Folder (Res)
In my case it works Fine
I tried all these things and none of them worked. One day all my projects are running, next day all my projects have an empty gen folder?
After a series of tests to resolve the phantom missing R.java, the one that led me to a drastic action is when I looked at the Properties > Android and the Project Build Target was greyed out and the project wasn't linked to any SDK, almost as if there were no SDKs installed. This was after I uninstalled 4.2 and reinstalled all tools and SDKs...
Long story short, after trying everything I could find online, I just deleted the whole "adt-bundle-mac-x86_64" folder in my workspace folder, unzipped the original download, and dragged the original folder back into the workspace.
This works as a last resort, however you will have to import all of your projects back into the package explorer by New > Project... > Android Project from Existing Code, and make sure you have the "Copy projects into workspace" UNCHECKED.
IMPORTANT: You will find that you can't do this if your "MainActivity" file is always named "MainActivity," so just for future project creating, it's good practice to always name your main activity something different each time.
This error occurred when I tried to graphically add a grid layout. Deleting the grid layout folder fixed the problem for me.
My solution was to install android sdk build tools with Android SDK Manager.
The probkem was that whenever I clean the project, the gen directory becomes empty.
Hope it will help!
if gen folder or R.java file is not generated then first check error in XML file and make sure android menifest.xml is present.
Right click on the project> Properties> Android > use the latest API
takes care of everything!
In my case, the solution was downgrading the target from android-22 to android-19 at project.properties