Why does the app signature change in Android after a classpath change?

Posted by espinchi on Stack Overflow See other posts from Stack Overflow or by espinchi
Published on 2010-03-16T23:29:40Z Indexed on 2010/03/16 23:31 UTC
Read the original article Hit count: 169

Filed under:
|
|

I have an Android project that branched into three different applications, app-1, app-2 and app-3, that apply some customizations. Currently there is a lot of code duplication, making maintenance a nightmare: do the changes in one of the branches, and then merge the other two.

So we create a library project, named app-core, that factors out most of the duplicated code. So far so good.

When I launch this into an emulator where the application was already loaded (before the refactoring), I get this exception:

Re-installation failed due to different application signatures

A different signature? But I just added a line in the .classpath to link to the app-core Java project!

The main question is: are the existing users going to be bothered by this too?

And the side question: Why is it a different signature?

© Stack Overflow or respective owner

Related posts about android

Related posts about classpath