Questions

Dear Median Support Team,

I am building an Android application called Freedom of Mankind using your platform, Median.co. I am currently trying to publish my app on the Google Play Console, but I am encountering an Android App Bundle signing-key error.

Google Play Console rejects my uploaded .aab file because it is signed with a different certificate from the one expected by Google Play.

The error details are:

Expected SHA-1 fingerprint: 7D:B7:1F:DD:E6:4D:2E:43:E9:06:24:A0:C3...

Uploaded bundle SHA-1 fingerprint: 1C:8A:2A:E7:EE:C1:E5:D7:B9:26:72:F1:96...

I would appreciate your assistance with the following:

Please help me identify why my Android App Bundle is being signed with a different key.

Please confirm whether my app is using the correct Android upload-signing key.

If possible, please help me rebuild my app using the correct signing key expected by Google Play Console.

If the original signing key is no longer available, please advise me on the safest way to resolve this issue without losing my existing Google Play app listing or release history.

I want to publish my application successfully and ensure that future updates can be uploaded without signing-key errors.

Please let me know what information you need from me to investigate this issue.

Thank you for your support. I look forward to your response.

Kind regards,

Freedom of Mankind Team

Project: Freedom of Mankind