Google play deploy workflow step error: Failed to perform edit insert call, error: Post "https://androidpublisher.googleapis.com/androidpublisher/v3/applications/com.shashank.composedemoapp/edits?alt=json&prettyPrint=false": metadata: GCE metadata "instance/service-accounts/default/token?scopes=https%!A(MISSING)%!F(MISSING)%!F(MISSING)www.googleapis.com%!F(MISSING)auth%!F(MISSING)androidpublisher" not defined (exit code: 1)

[ShashankEd]

Hi All,

I have setup a workflow for CI-CD for my android build, and targeting the internal track to update the build.

I am trying to deploy my build to my internal test track, the "Android Build" work flow is getting completed, but when the "Google play depot" step is starting, getting the below error:

Getting configuration Configs:

• service_account_json_key_path: *****
• package_name: com.shashank.composedemoapp
• app_path: /bitrise/deploy/app-release-bitrise-signed.apk\n
• expansionfile_path:
• track: internal
• user_fraction: 0
• update_priority: 0
• whatsnews_dir:
• mapping_file: /bitrise/deploy/app-mapping.txt
• release_name: 1.0.1
• status: 0
• retry_without_sending_to_review: false
• ack_bundle_installation_warning: false
• verbose_log: false Using mapping file from: /bitrise/deploy/app-mapping.txt Using app from: /bitrise/deploy/app-release-bitrise-signed.apk Configuration read successfully

Authenticating Authenticated client created

Create new edit Failed to perform edit insert call, error: Post "https://androidpublisher.googleapis.com/androidpublisher/v3/applications/com.shashank.composedemoapp/edits?alt=json&prettyPrint=false": metadata: GCE metadata "instance/service-accounts/default/token?scopes=https%!A(MISSING)%!F(MISSING)%!F(MISSING)www.googleapis.com%!F(MISSING)auth%!F(MISSING)androidpublisher" not defined

I've tried to find any possible solutions for this, but couldn't get. Please help me as I am totally blocked on this.

[bitrise-coresteps-bot]

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]

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.