Android: Error - App has same packaged different signature

Question

I am getting an issue where android studio is saying

 Installation failed since the device has an application with the same package but a different signature. . . .. 

This is correct, as I recently signed an APK and uploaded to the beta area of my play developer console.

And now I am trying to debug it locally and by default I believe that all Android projects are signed by the debug keystore hence the signatures would be different.

What is the best way to deal with this? Would it be possible to sign my debug version with my release key, and is there a potential danger here?

How would I force the signing of my debug version with my release keystore without losing the ability to debug, etc.?

Or should I just keep uninstalling and reinstalling the different versions - that seems the worst possible workaround. :-)

Kenyettakenyon

Answer 1

You can sign your apps with your release key while keeping the debugging option - you just have to add your release key into Android Studio (or specify it on the command line if you are signing your apps there).

In Android Studio, right click on your app in the project browser and open module settings. Select your app's module and click on 'Signing' to make sure your release keystore is listed. Then under 'Build Types', make sure that the debug target and the release target share the same signing config, and that the debug target has debuggable set to true. They should now share the same key.

More information on app signing can be found in the Developer docs here.

I haven't heard of a downside to using the same key for debugging and for release, provided the private key is kept secure (read: not under version control).

Stans

Hey, I tried to follow along but I don't see "Signing" button, only "Signing Config" tab. I tried to set it up but it didn't work. Help? – Anthelion

Answer 2

In my case after upgrading Android Studio, I had removed the $HOME/.android folder which made Android Studio create a new $HOME/.android/debug.keystore. After copying the old debug.keystore it worked again.

Collateral

Good thing I had a backup of that folder before I carelessly blew it away! – Bonedry

I moved my old machine $HOME/.android/debug.keystore (where i was developing) to new machine and it worked, thanks – Endamoeba

Answer 3

try change debug to release in builds variants

Meantime

Answer 4

In my case, the problem was fixed by adding the SHA-1 and SHA-256 certificate fingerprints given in Android Studio (click on Gradle on the right side of the AS window, then run configurations and signingReport) to your Firebase project settings->General->SDK setup and configuration.

By the way, this also solved the problem I was getting logging in and getting the cryptic error Activity.RESULT_CANCELED.

Consolidation

Answer 5

changing the app id in gradle files did it for me

    defaultConfig {
    applicationId 'com.example.app'
    }

Dygall

Not a good solution since you still want android to acknowledge it's the same app – Anthelion