Can't Upload APK because 403 but Edit insert is created

[pedromalta]

That's the log I'm getting trying to use the step on bitrise: What I find weird is that the Edit is being created, but the upload is failing.

``+------------------------------------------------------------------------------+

(8) google-play-deploy@3	+------------------------------------------------------------------------------+	id: google-play-deploy		version: 3.0.2		collection: https://github.com/bitrise-io/bitrise-steplib.git		toolkit: go		time: 2020-06-10T13:56:41Z	+------------------------------------------------------------------------------+

Getting configuration Configs:

• JSONKeyPath: *****
• PackageName: fm.[REDACTED].music.alpha
• AppPath: /bitrise/deploy/app-alpha.apk
• ExpansionfilePath:
• Track: internaltest
• UserFraction: 0
• WhatsnewsDir:
• MappingFile: Found .apk file: /bitrise/deploy/app-alpha.apk Configuration read successfully Authenticating Authenticated client created Create new edit editID: 00542497222085258217 Edit insert created Upload apks or app bundles Found .apk file: /bitrise/deploy/app-alpha.apk Uploading /bitrise/deploy/app-alpha.apk 1/1 Failed to upload APKs: failed to upload apk, error: googleapi: got HTTP response code 403 with body: Access Not Configured. Google Play Developer API has not been used in project 141409347850 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/androidpublisher.googleapis.com/overview?project=141409347850 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry. | | +---+---------------------------------------------------------------+----------+ | x | google-play-deploy@3 (exit code: 1) | 14.70 sec| +---+---------------------------------------------------------------+----------+ | Issue tracker: https://github.com/bitrise-io/steps-google-play-deploy/issues | | Source: https://github.com/bitrise-io/steps-google-play-deploy | +---+---------------------------------------------------------------+----------+ ``

[pigeon-archive]

Hi @pedromalta,

Can you please share a build link and enable support access in your project setting?

[pedromalta]

Hi @non-binary I enabled the support access. The build that is giving us trouble is that one https://app.bitrise.io/build/a4a1d63dce32dc56#?tab=log

[pigeon-archive]

Hi @pedromalta,

Please take a look at https://github.com/bitrise-steplib/steps-google-play-deploy/issues/53.

[pigeon-archive]

Hi @pedromalta,

Please also follow the documentation on how to set up a service user: https://devcenter.bitrise.io/deploy/android-deploy/deploying-android-apps/#setting-up-your-first-project/

[garthus]

Hi @non-binary

I am also having this issue and also seems to be widerspread if I am correct:

https://github.com/fastlane/fastlane/issues/16593

I have also gone through the above docs many times, setup and resetup and cannot get it to deploy to the play store.

One occasion it worked but not since

[nicolasjafelle]

We are also facing this issue for our builds.

[bitce]

We're seeing other reports of the problem no longer happening. Can you guys let us know if you still get this error?

[nicolasjafelle]

Still happening to me, more specifically this one: https://github.com/bitrise-steplib/steps-google-play-deploy/issues/87

[github-actions[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.

[github-actions[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.