The library-based application installs 2 APK files, and not one - Why?

I am trying to restructure an existing application, so that, with the exception of a few redefinable methods in a derived activity, all the code will be in the library. This still does not work for some reason , but in the process of trying to fix this problem, I found, much to my disappointment, that there are two .apk and not one (when I start a debugging session from eclipse):

  • The first (and larger file) with the original library name.
  • The second (only 20 KB) with the name of the derived application.

Why is this and where can I find out more about it?

Could this explain the ClassNotFoundException problem with me?

+4
source share
1 answer

I myself found the answer. It turns out that I had two critical settings in the properties of both projects that were not installed correctly:

  • In the library project, the Library was not checked for some reason. I could swear I checked it, but knowing how fancy the Android Eclipse development environment may be, I suspect that it was not marked by Eclipse (or the ADT plugin) as a result of some failure.
  • In the application project I neglected adding my library project as a link via the Add ... button. (how could I be stupid?)

Hoping this may be useful for other newbies.

+4
source

All Articles