Could not find Library.apk!

I found the source of the problem!

It turns out that "with the new library feature, you don't specify the Android projects you depend on in the Java Build Path section of the Properties. You do it in the Android section of the Properties".

So all I had to do is go the Application Project's Properties, hit the Projects tab, select my own library project and click the Remove button. That's it. No more problem.

In Eclipse Java EE select the project Properties, then select Project References, then check the FacebookSDK (see screen capture)

Thanks to Lance Nanek!

That's interesting... I didn't quite do what the answer specifies..

I have a separate android project called "ConnectionHandler" which connects to a webservice to retrieve information. This project contains no activity classes. (If it did, you would require changes to the AndroidManifest file in your Main Application, as well as following the instructions below).

To use my seperate ConnectionHandler project as a library I needed to do the following:

1. In the Main Application > Select project properties > Go to Java Build Path > Add Jars > Select the bin folder of ConnectionHandler > choose connectionhandler.jar
2. In the ConnectionHandler project > Select project properties > Android > Check isLibrary
3. In the MainApplication > Select project properties > Go to Android > Add reference to ConnectionHandler in the Library section.

This works for me, and I am able to connect to my webservice, even though I have no source files to do this in my main application. Everything is contained within my ConnectionHandler jar that is being referenced..

Hope this helps someone...

Today I started getting this error message on the Console view of Eclipse, but it turns out that this was not the problem. My application would be built and installed on my device, and even ran for a fraction of a second (until it crashed). This is what my Console view looked like on Eclipse:

[2013-06-03 09:42:25 - my-android] Android Launch![2013-06-03 09:42:25 - my-android] adb is running normally.[2013-06-03 09:42:25 - my-android] Performing com.my.android.activity.MainActivity activity launch[2013-06-03 09:42:25 - my-android] Uploading my-android.apk onto device '650rfs2e'[2013-06-03 09:42:31 - my-android] Installing my-android.apk...[2013-06-03 09:42:35 - my-android] Success![2013-06-03 09:42:36 - my-other-android] Could not find my-other-android.apk![2013-06-03 09:42:36 - android-SherlockFragment] Could not find android-SherlockFragment.apk![2013-06-03 09:42:36 - my-android] Starting activity com.my.android.activity.MainActivity on device 650rfs2e[2013-06-03 09:42:36 - my-android] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.my.android/.activity.MainActivity }

But upon close inspection of my LogCat, there was a silly exception being thrown from a fragment I was trying to initialize. Once I fixed my fragment (which was raising an NPE), everything worked out just fine, even through my console still tells me it can't find those library APK's.