This would be a onetime process. Inorder to get your signature you would have to temporarily enable debugging on the release version of the app and sign the app. Don’t worry you don’t have to publish the app you just want to take a look at the logs for the release version.
Change the releaseImplementation to point to ‘com.github.mukeshsolanki.Android-Tamper-Detector:tamperdetector-no-op:1.0.0’ to your app/build.gradle file
Adding the debuggable true to your app/build.gradle file
...
buildTypes {
debug {
}
release {
debuggable true // This is the temporary flag we added. Please remove this once you have got the signature
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
...
Next we are going to call the getSignature() to get and log our signature. Open Splash.java file in android studio then go to line 154 or search for this line Log.d("Signature", AppSignatureValidatorKt.getSignature(this));. this line should be Commented you have to uncomment this line
Sign the app and run the release version and look at logcat. You should be able to see your release signature on the console. Note it down and then we can use this to securely validate your apk using validateSignature(). Please remove the debuggable flag (Line: 37) and change the releaseImplementation to the original one back (Line: 254) once you have noted down the signature. Also the getSignature() method only works on the debug version and not on production
Now You can add the signature you noted to the Firebase Remote config to enable it. if you dont have the option to add signature to your firebase then you have to update your firebase remote config to the latest. we provided that with downloaded file. You have to do the same steps you have done to install the remote config but this time you have to use the latest json. so that this will overwrite your old firebase remote config.