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

Question

I have an Android project that branched into three different applications, app-1, app-2 and app-3, that apply some customizations. Cur

Answer 1

For this problem u need to check that the correct key is used under (Window->Preferences->Android->build). This u can check from the android.mk file of the app. And on placing the correct key path , CLEAN and BUILD the project to avoid this error .

Answer 2

Uninstall the application on the device, then run code again, it will work. It happens for me and I tried same thing, now it is working correctly.

Answer 3

I have had the similar kind of issue. If you are installing it on your device then you need to uninstall the app on your device prior to install it from eclipse. It will definitely solve your problem.

Cheers

Answer 4

The digital signature is driven by a signing key that exists on the machine that signs the app. If Developer A compiles an app using the standard debug key and installs it in an emulator, then tries installing some other variation of the app -- one signed with a production key, one signed with Developer B's debug key, etc. -- in the same emulator, you will get that error.

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

Do you have the production signing key that you used for the version of the app your existing users are using? If yes, then there should be no problem. If no, you're screwed.