search

bitrise-steplib / steps-google-play-deploy

MIT License
54 stars 35 forks source link

failed to create auth config from json key file #148

Closed Cash39406 closed 8 months ago

Cash39406 commented 1 year ago

I tried to deploy aab file to play store but encountered this error:

Authenticating Failed to create HTTP client: failed to create auth config from json key file [REDACTED], error: %!s() Failed to create HTTP client: failed to create auth config from json key file [REDACTED], error: %!s()

Log is here: https://app.bitrise.io/build/ce924ad0-619d-4cea-a099-dd089e7c820c

bitrise-coresteps-bot commented 12 months ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

rsweny commented 12 months ago

For me I had to do the opposite of what the instructions say.. just upload the json key file under "Code Signing and Storage" and copy the variable that begins with $BITRISEIO_ .... _URL and use that in the "Deploy to Google Play" step.

Use this variable directly and do not create a secret that holds it. Hiding an environment var name behind a secret did seem rather pointless as it is the url that needs to be kep secret.

bitrise-coresteps-bot commented 8 months ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

bitrise-coresteps-bot commented 8 months ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.