Questions

Hello Median team,

I’m currently preparing my Android app, AJ, for publishing on Google Play Console.

I generated the Android AAB using Median, but I’m having an issue with the Android signing/upload key.

Google Play Console is telling me that the signing/upload certificate associated with my uploaded AAB does not match the key currently expected by Google Play Console. I tried requesting an upload key reset, but Google is asking me to provide a new upload certificate/key.

I need to know:

1. Where can I find or obtain the Android keystore/upload key or certificate that Median used to sign my AAB?
2. Is the signing key stored somewhere inside Median App Studio?
3. If it is not accessible to customers, can Median provide the SHA-1/SHA-256 certificate fingerprint or the appropriate certificate file needed for an upload key reset?
4. If I need to generate a new upload key, what exactly should I provide to Median/Google Play so that future AAB builds from Median will work correctly?
5. Is there a specific Median setting I need to change so that the signing key remains consistent for future builds?

I am trying to avoid starting my Google Play app setup over, so I would appreciate the safest step-by-step solution.

Thank you for your help.