Closed wverdese closed 1 year ago
github-actions[bot]
commented
1 year ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
eirikvaa
commented
1 year ago It would be great to get some input on this issue.
SUPERCILEX
commented
1 year ago This is highly unlikely to be a bug with the plugin. You've configured the wrong signing key which has nothing to do with the plugin IIRC. An easy way to check this is to extract the built aab from CI and manually upload it to the play store. You'll almost certainly find that it fails with the same error indicating that your CI key config is wrong.
wverdese
commented
10 months ago An easy way to check this is to extract the built aab from CI and manually upload it to the play store.
For future reference: you were right. We found the error on our side. Sorry for this!
Describe the bug
I am currently experiencing an issue with the Gradle Play Publisher when deploying Android apps to the Google Play Store via a bash script called from a GitHub Action. Specifically, the problem is related to a key signature mismatch. This issue is very similar to #896 .
I receive the following error message during deployment:
(I have manually replaced the two different SHA-1 I see in the original error message with placeholders).
The weird part is that, if I call the same bash script locally from the terminal, everything works fine and the .aab gets published successfully on the store.
Additional Information:
The service account JSON file used for authentication is consistently the same in both my local environment and GitHub Actions.
The environment variables, configurations, and the keystore (JKS file) used for signing the APK are identical in both environments.
Gradle Wrapper: The Gradle wrapper version is the same in both environments.
Caching and GitHub Secrets: I have verified that secrets and cached files (e.g., keystore and service account JSON) are being properly accessed and utilized in the GitHub Action workflow.
Google Play Console Configuration: The Google Play Console configuration, including the application package name, certificate fingerprint, and other details, matches the credentials and keystore.
Permissions and Quotas: The service account has the necessary permissions, and there are no quotas or rate limits affecting the deployment process.
How To Reproduce
Run the GitHub Action workflow for deploying an Android app to the Google Play Store's internal track using Gradle Play Publisher.
The actual behavior is that during the deployment process, a key signature mismatch error occurs. The error message indicates that the Android App Bundle was signed with the wrong key, even though the environment, credentials, and configurations are consistent between my local environment and GitHub Actions.
Versions
Tasks executed
Expected behavior
I expect that when deploying the Android app to the Google Play Store using the GitHub Action workflow, the deployment should proceed without any key signature mismatch errors. The app should be successfully uploaded to the Play Store's internal track.
Additional context (if a crash, provide stack trace)