Changing the debug build signature of the android app to the release signature is useful in many ways.

Introduction

It's different from the debug build signature for android apps, usually the release build signature.

Well, the keystore for release build signatures is important, so it's best to limit usage, but changing debug build signatures to release build signatures can make development a lot easier.

You can overwrite the debug version on the release version.

How to do

signingConfigs {
        //Release DEBUG version Enable this when you want to build build sign
        debug {
            storeFile=file(project.properties.storeFile)
            storePassword=project.properties.storePassword
            keyAlias=project.properties.keyAlias
            keyPassword=project.properties.keyPassword
        }
    }

Just add something like this.

effect

--You can overwrite the release app from android Stuido. With this, you can do various things using the production data. For example, debug of data migration at the time of version upgrade. --You can authenticate with the debug version without registering the debug keystore on the server side such as google authentication. --Debug installation does not fail when the release version is installed on the device. I can't ask to uninstall it one by one. This is really annoying. When it comes to the initial installation, various things disappear. --For some reason, I couldn't read the serialized data. I'm excluding obfuscation ...? I wonder if the obfuscation status of the dependent class is different.

Summary

No, it's really convenient. I regret that I should have done it sooner these days: joy: No, I knew from before that I could change it, but when I was driven by the need, it was already ...

If there is no security problem, it is recommended. Well, only if the package name is the same.