search

bitrise-steplib / steps-google-play-deploy

MIT License
54 stars 38 forks source link

Failed to upload APKs: failed to upload apk, error: googleapi: Error 403: APK is not a valid ZIP archive, forbidden #89

Closed SaravanarajaGITHUB closed 3 years ago

SaravanarajaGITHUB commented 4 years ago

Facing this issue, no solution found in net & also with this related issue link too #86

Build URL --> https://app.bitrise.io/build/b0b1aaa5b60b9dd5#?tab=log

Capture

lucasfronza commented 4 years ago

Facing the same issue

jgersonde commented 4 years ago

Same issue !!!!!

ibushi-gs commented 4 years ago

Facing the same issue.

fwvictor commented 4 years ago

Same issue!!

srikanthreddi4u commented 4 years ago

facing the same issue , any update?

david-alejandro-reyes-milian commented 4 years ago

same here, obviously something changed in the store. Checking out

SergiyDivnych commented 4 years ago

Same issue!!

dfabulich commented 4 years ago

There's a substantial discussion about this on the fastlane issue. The fastlane developer reached out to Google and had confirmation that it's a known issue. Follow that thread for more status updates.

tuanta429 commented 4 years ago

Same here!

jamesjara commented 4 years ago

we are having the same problem

sonny-kava-up commented 4 years ago

^ +1

bitce commented 4 years ago

Hi everyone!

Sorry for the silence on this issue so far. As @dfabulich mentioned, the issue seems to be related to the Google Play store and has an intermittent nature - I have several users confirming that deployment works as expected by now.

What's important is that this issue only affects APKs and is only happening when using their API. So uploading a release manually or deploying bundles should work.

We're still looking into what's happening exactly, will keep everyone updated here.

github-actions[bot] commented 3 years 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.

github-actions[bot] commented 3 years 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.