I think the title describes the problem. I have already followed this , added appcompat as a library in my project.But still getting this error. What can I do?
I have found solution to this problem. I am giving it here. May be it will help somebody.
In my project I needed appcomat_v7 support library. I added appcompat_v7 support library correctly as instructed here. But still it was showing that error. Its because appcompat_v7.jar was missing from */android-support-v7-appcompat/bin folder as android-support-v7-appcompat project was not building properly and creating that jar file. It was happening because of this Parsing Data for android-21 failed error. I have installed JDK 1.8.
Then clean & build appcompat. This time appcompat_v7.jar was created. Then clean & build my project. And it worked!
Related
I am trying to build my project on device and having problem with library configuration for App-v7-appcompact from the screenshot as below.
I have successfully added App-v7-appcompact into Eclipse project and also tried adding manually in Eclipse folder but having same errors even I added to build path aswell. I dont know what is problem with Appcompact-v7-library, plz help me in fixing my issue so I am able to run application on device.
I also added libraries in properties aswell.
check here this is very helpfull http://developer.android.com/tools/support-library/setup.html
I have a problem importing the PagerSlidingTabStrip library into Eclipse, I get multiple errors and I know this happens because the library was built using gradle.
I tried to follow this answer but I can't find use as source folder in the build path menu.
I've never used gradle previously and don't know how to go about this in Eclipse. Please guys, help most of us who have this problem out of our dilemma. Would be very grateful.
Okay in the end this was what i did:
I checked the build.gradle file of the library for target and min sdks. I then put what i found in the android manifest.xml which I know Eclipse uses.
I deleted the build.gradle and gradle.properties files.
Made sure the project was marked as a library. And it works!
I think the most crucial step was to check the build.gradle for the sdks and whatever else the project requires and replicating that the way it should be in the manifest file.
Today, I updated my Android SDK and Eciple ADT to the most recent versions (ADT Rev 22). After restarting Eclipse it is quite unhappy with the Build Paths whenever I reference custom libraries.
An example is shown in this screenshot:
My custom "Android Utilities Library" compiles fine, but everything that depends on it shows build path errors. E.g. when I investigate the build path settings for "Android URA Library" it shows me an error with the android_utilities_library.jar missing under "Android Dependencies" (which in fact is true, the libraries will be built to individual class files in bin/classes).
After reading the solution to Build path errors with library projects I tried to clean and manually build my projects in the correct order, but to no avail.
I've never dealt with this before, so I don't know how to attack the problem.
Any help is appreciated. Thx!
Installing the new Build Tools did the trick. They were not automatically included when I updated the SDK (probably need to run the update twice I guess).
I found a solution that works for me:
Go to Project Properties > Build Path > Order and Export
Then you have to check each checkbox.
In my case my libraries were restored
I hope it will help.
I can see that your project Android URA Library is referring to Android Utilities Library, then the problem should not relate to SDK/ADT update.
Please check:
Project Properties of Android URA Library, choose Project tab and make sure you added Android Utilities Library as dependency project. Otherwise, please add it.
If the problem is still existing, then Projects \ Clean All Projects
Go to libraries and check the build path of the dependent libraries. It should be same as your projects build path.
if you have import all the Dependencies in your workSpace.maybe you can:projetc-->build all.
I meet the problem,and it works well
Help needed!!!! Stuck for 2 weeks on this and help needed.
I've recently imported the facebook sdk for android and its projects into my workspace. It shows up errors and the problems:
Archive for required library: '/home/Documents/facebook-android-sdk-3.0.2.b/facebook/libs/._android-support-v4.jar' in project 'FacebookSDK' cannot be read or is not a valid ZIP file
And the samples get errors along the line of:
The container 'Android Dependencies' references non existing library '/home/Documents/facebook-android-sdk-3.0.2.b/facebook/bin/facebooksdk.jar'
The things I have done following the other discussions without any success are
cleaned project
set the Facebook SDK as library
looked at the build path section and added external jar consisting of facebook/libs
imported fb sdk like 20 times and into different folders.
made sure my java compiler was 1.6
HELP would be very greatly appreciated!!!!
Take the lastest version of android-support-v4.jar (in your sdk environement : sdk/extras/android/support/v4/android-support-v4.jar) and replace in your project and library project do not create conflict.
The steps to importing a library are:
Download the library
Place the library in the libs folder of the project.
Build the project
Do Not attempt to import the library using some import wizard.
I suspect either your download was corrupted, and you need to do it again, or you put the file into the wrong directly.
I think your problem is that the android.support.v4 versions are different, take the one from your project and replace the one in the Facebook sdk lib folder, it should dismiss the clash.
As per your question, I think you are not able to compile once you add the SDK to your project. Do you get an error saying unable to run as library?
If so that means you have included this as library and create your project as a library to be used further. It is a common mistake that I have seen many people do when they try to import a library to use and tick mark the checkbox is Library. This actually means you want this project to be treated as a library for future use. Just try to add the SDK and do not tick mark the checkbox and this project will run fine.
Many forums will just tell you to tick that checkbox and you will be stuck on this error for long time.
For any .jar file related issues you have to make the .jars files compatible as there hashing a problem and the two jars are not compatible with each other (a version issue).
although there are many questions with a similar title, I could not find the solution to this issue.
I have an Android project in Eclipse which references ActionBarSherlock 4.0.2 as Android library. In addition, I have added the JARs for ACRA and Google Analytics in the /libs folder. The support v4 jar is taken from ABS libs.
The project's Java Build Path looks like this
When exporting through the wizard I get the "Conversion to Dalvik format failed with error 1" error.
Cleaning, removing all Android Dependencies and clicking on Fix Project Properties and cleaning does all not work.
Any idea?
EDIT:
I missed some info: I'm doing this on Mac OS 10.6.8, Eclipse Indigo, Android SDK Tools r19 and ADT plugin v18.
project.properties file includes the proguard.cfg file: commenting it does avoid the issue.
I actually managed to overcome the issue, here soem details if they can be of use to anybody:
I first tried everything from clean to close/reopen project etc etc etc
I finally too the latest beta of proguard from http://sourceforge.net/projects/proguard/files/ and replaced the /lib folder in android-sdk-macosx/tools/proguard with the one from the beta version (proguard4.8beta1) and .. it works!
I had the same issue after updating to ADT 20 (released with Jelly Bean), and similarly, all the old solutions (clean, rebuild, etc.) didn't help. Taking a clue from omoling's answer, I updated my Flurry jar to the latest from their website... and the problem cleared up.
So, if you're having this problem, try updating any/all external libraries that your project uses.