73

I managed to restructure my application pretty nicely so that, except for a few methods in a derived Activity class, everything is in a Library Project.

It works beautifully, except that Eclipse's Console (not LogCat!) issues the following error message:

[2011-06-13 19:54:08 - MyLibrary] Could not find MyLibrary.apk!

I cleaned both projects (library and application), restarted Eclipse, re-built the projects, but this weird error message persists.

What does this error message mean? (especially in light that everything seems to be running OK)

How do I get rid of it?

UPDATE: I tried removing the project then re-importing it per the suggestion below. It didn't help. I then found this thread that helped me realize that I had <uses-library> in the application's AndroidManifest.xml referring to MyLibrary. I deleted it, cleaned the project and rebuilt. The problem persists.

I am now suspecting this is "real problem", e.g. misconfiguration of some paths or something else on my part. What could it be?

Improve this question

7 Answers 7

Reset to default
162

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) enter image description here

Thanks to Lance Nanek!

Improve this answer
10
  • 3
    I have tired this, and it does resolve the issue in question, however now when I do an "Open Declaration" on say a class defined in my library, it opens MyClass.class file, it should open MyClass.java file. Another SO question regarding opening of .class instead of .java (stackoverflow.com/questions/9682074/…) suggests to add the library project as a project reference in the build path! So it would seem that there isn't a way to fix both issues at the same time? (Using Eclipse 4.2.0, JDT 3.8.0, ADT 20.0.3)
    – Herr Grumps
    Commented Oct 29, 2012 at 15:01
  • 3
    I found the wordage here a bit confusing, but it is the right answer. Lance Nanek describes more clearly to go to "Java Build Paths", select Projects tab, and remove the library from there.
    – Alan Moore
    Commented Jan 14, 2013 at 4:29
  • 5
    after doing remove, my app can't find symbols in my lib, and this will help: With this 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.
    – Bill Hoo
    Commented Jul 9, 2013 at 3:27
  • 1
    After doing that, I can't import Facebook classes in my project anymore. Eclipse can't find them
    – LeSam
    Commented Feb 7, 2014 at 3:20
  • 1
    After following the steps of the OP's answer, you need to right-click on your app project, click Properties, click Android, and in the Library section tick the Add button and add your Library project. Then everything should work as expected with no error messages shown.
    – Boycott A.I.
    Commented May 8, 2014 at 14:31
4

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...

Improve this answer
2

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.

Improve this answer
1

Have you tried removing the project without deleting from the harddrive and reimporting the project. That seemed to work for me when I had this problem.

Improve this answer
3
  • 2
    Are you saying that programming nowadays has become more like Voodoo and less like science? :) I will try your suggestion and report back. In the meanwhile, +1 for the attempt to help.
    – an00b
    Commented Jun 14, 2011 at 13:48
  • I just tried removing the application project only then re-importing it. It didn't help. I will now try removing the library project...
    – an00b
    Commented Jun 14, 2011 at 14:03
  • I just tried removing the library project as well then re-importing it. It didn't help. I am now suspecting this is real problem, e.g. misconfiguration of some paths or something else on my part. What could it be?
    – an00b
    Commented Jun 14, 2011 at 14:08
0

Using the Eclipse Preferences you can end up with libs getting added all over the place. I had a referenced lib in /libs and Referenced Libraries folders. I had to remove or delete them from these locations and insert it at Android Dependencies (using Preferences -> Android and browsing below the "Is Library" checkbox.)

The correct layout for my project: http://www.pasteall.org/pic/show.php?id=34513

Improve this answer
0

For me, the reason this was happening was that the library project and the main project had the same package. The easiest way to change the package is to right click on the library project > Android Tools > Rename Application Package.

Improve this answer
0

The solution to this problem for me, was to remove erroneous entries from the library projects' Manifest file.

The crash would only occur at runtime when it hit the first usage of my library project. Once I change the Application Name property to reflect the correct application class for the project that used the library project, then it worked

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.