CODEWITHSUNDEEP
androidandroid-studiokeystoresignatureandroid-keystore
Jikiwiki
Jikiwiki

Reputation: 115

Application with the same package but with a different signature

I upgraded my Android studio to 1.4. Now when I'm deploying my app to my device I get the message that the device has an application with the same package but a different signature. How is this possible? I already did some research and I looked up my debug.keystore, but this hasn't changed since 13/03/2015. Anyone has any idea how I can fix this?

Upvotes: 1

Views: 6518

Answers (2)

Sanjeev Sangral
Sanjeev Sangral

Reputation: 1417

The problem is the keys that have been used to sign the APKs, by default if you are running directly from your IDE and opening your Emulator, the APK installed in the Emulator is signed with your debug-key(usually installed in ~/.android/debug.keystore), so if the previous APK was signed with a different key other than the one you are currently using you will always get the signatures conflict, in order to fix it, make sure you are using the very same key to sign both APKs, even if the previous APK was signed with a debug-key from another SDK, the keys will definitely be different.

Also if you don't know exactly what key was used before to sign the apk and yet you want to install the new version of your app, you can just uninstall the previous application and reinstall the new one.

for more info go through This

Hope this Helps...

Upvotes: 2

Daniel Zolnai
Daniel Zolnai

Reputation: 16910

Debug builds are signed with the SDK keystore which is generated when you install the Android SDK. On Linux / OSX it is located at ~/.android/debug.keystore. The message you had means that you have a debug build installed and you want to install an App Store build on it (or the other way around). This can also happen when you deploy from a different machine.

Upvotes: 1

Related Questions