Home/ Questions/Q 8783273
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T20:47:17+00:00

I have an Android application project (A) and an Android library project (L). A

  • 0

I have an Android application project (A) and an Android library project (L). A uses L as a library.

L, the library project, uses a few external libraries already: Apache Commons Codec 1.7, Apache Commons Lang3 3.1, the Android Support library V4, and ActionBarSherlock 4.0, referenced as a library project. All of these libraries, and the code that calls them, work perfectly fine, and have been working fine for a while.

However, I recently added one more library: Apache Commons IO 2.4. Now my application crashes any time the library code (in L) tries to call a method in Commons IO.

I’ve added the IO library in exactly the same way as I’ve added every other external library: build path

When my application first starts I get:

11-01 12:32:14.243: I/dalvikvm(3815): Could not find method org.apache.commons.io.FileUtils.copyInputStreamToFile, referenced from method au.com.grdc.alib.helpers.LibraryCommon.download
11-01 12:32:14.243: W/dalvikvm(3815): VFY: unable to resolve static method 7039: Lorg/apache/commons/io/FileUtils;.copyInputStreamToFile (Ljava/io/InputStream;Ljava/io/File;)V

Later on I get:

11-01 14:50:48.913: E/AndroidRuntime(10030): FATAL EXCEPTION: AsyncTask #1
11-01 14:50:48.913: E/AndroidRuntime(10030): java.lang.RuntimeException: An error occured while executing doInBackground()
...
11-01 12:35:10.268: E/AndroidRuntime(4493): Caused by: java.lang.NoClassDefFoundError: org.apache.commons.io.FileUtils
11-01 12:35:10.268: E/AndroidRuntime(4493):     at au.com.grdc.alib.helpers.LibraryCommon.download(LibraryCommon.java:89)

I saw that it was recommended to rename my “lib” folder to “libs”, which I’ve done — this hasn’t fixed the problem.

I also saw recommendations to mark external libraries to be exported, which I’ve also done, and which also hasn’t fixed the problem.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    1. Update your eclipse-android-plugin and android-tools (They have changed how libs are handled a while ago)
    2. Make sure, that you have in your project the ‘libs’ (not ‘lib’) folder.
    3. Put all your library jars in the ‘libs’ folder.
    4. Make sure that your library jars in the ‘libs’ folder are NOT added to the build path like you would in plain java projects. Android will add them automatically. If you look at Project > Properties > Java Build Path > Libraries:
      1. Ensure that there is no single one of your library jars shown on the top-level (remove them otherwise)
      2. Check that there is an auto-created top-level dependency group called ‘Android Dependencies’.
      3. Check that all your jars from the libs folder have been automatically added to the ‘Android Dependencies’ group

    Do the above steps for both, (A) and (L).

    Also ensure that (A) has no plain-java-style project dependency on (L).
    Project > Properties > Java Build Path > Projects for (A) should not list (L), remove otherwise.

    Ensure that Project > Properties > Android for (A) lists in the Library section project (L), add otherwise.

    • 0