09 Apr 2018 06:27 AM - last edited on 09 Dec 2021 02:16 AM by MaciejNeumann
After the instrumentation on Android, when uploding the file in Play Store, the Application starts using an Dynatrace Certificate and I would like to use my own certificate. Is there a way to easily change the appointment?
Solved! Go to Solution.
Our gradle plugin is doing this step already, but if you use the instrument.cmd/sh, you have to use the apksigner after the instrumentation. See here: https://developer.android.com/studio/command-line/apksigner.html - So if possible use the dynatrace gradle plugin.
Auto-instrumentation generates a working folder (with the name of the APK file) at the location of the provided APK file and stores the result in the dist folder. The path to this folder will be <pathToYourApk>/<nameOfAPK>/dist/.
There are three APK files in this folder:
I am guessing you are uploading the final.apk file (Option 3 above) with the Dynatrace debug certificate.
To upload your mobile app on Google Play, you have to sign the instrumented APK <pathToYourApk>/<nameOfAPK>/dist/<nameOfAPK>.apk (Option 1 above) with your Google Play certificate. The auto-instrumentation script does not automatically sign the instrumented APK file with your Google Play certificate. Therefore, you have to do this step manually. First, you have to zipalign the APK file and then you have to use the tool apksigner to sign the APK file with your Google Play certificate.
Go to link and scroll to the bottom of page for more info (This applies to auto instrumentation from the command line)
Hope This Helps
Thanks guys, Im going to test and go then I back to you with the result.