search

bitrise-steplib / steps-google-play-deploy

MIT License
54 stars 38 forks source link

Bug - 502 #108

Closed billnbell closed 3 years ago

billnbell commented 3 years ago

Started getting this error. Committing edit Failed to commit edit, error: googleapi: got HTTP response code 502 with body: <!DOCTYPE html>

Error 502 (Server Error)!!1

502. That’s an error.

The server encountered a temporary error and could not complete your request.

Please try again in 30 seconds. That’s all we know.

trestini commented 3 years ago

Same here. It appear to be a problem with Google, but I've tried 3 builds in a 3 hours timeframe with the same error.

billnbell commented 3 years ago

OK any way to fix it? Did they change their Authentications?

bandojulio commented 3 years ago

I got the same error but my .aab was uploaded successfully to the play store. Just got my pipeline broken because of the 502 error

billnbell commented 3 years ago

same here. It uploaded but I get a 502.

bandojulio commented 3 years ago

I've put this step as the last one in my pipeline since it's uploading successfully. I looking for release notes or system status of the Google Play Android Developer API, if someone find it we can check if some major chance broke this step.

AlbertoSaezVela commented 3 years ago

The same here. Anyway, the app was correctly uploaded to PlayStore.

Version used for google-play-deploy 3.0.2

Request:

Failed to commit edit, error: googleapi: got HTTP response code 502 with body: <!DOCTYPE html>

Error 502 (Server Error)!!1

502. That’s an error.

The server encountered a temporary error and could not complete your request.

Please try again in 30 seconds. That’s all we know.

jeanremy commented 3 years ago

Same here. Upload works, but google-play-deploy fails. Is it related to Google changing their routes ?

bitce commented 3 years ago

Hey everyone! Sorry to hear about the errors, we're looking at this right away. Can anyone provide a link to their build URL or a logfile? That would be helpful in further digging into this.

Thanks!

adebree commented 3 years ago

Hey everyone! Sorry to hear about the errors, we're looking at this right away. Can anyone provide a link to their build URL or a logfile? That would be helpful in further digging into this.

Thanks!

I've reached out to you on the Bitrise slack for this

mabdurrahman commented 3 years ago

I'm experiencing the same issue too, clearly, it's an issue from Google side as I can get a similar issue when I upload the build manually from Google Play Console just after clicking on "Start rollout to Internal testing":

An unexpected error has occurred. Please try again. (5039F17F)
androideveloper commented 3 years ago

The same here

MarcosEduardoJr commented 3 years ago

The same here, pls save us im crying

noakk commented 3 years ago

The same here =/////

mackoj commented 3 years ago

same here

duy-ng-12354 commented 3 years ago

Same here. the app is deployed successfully but we cannot be comfortable with a 'red' build.

image

Please help to address this issue.

Thanks a lot.

jamieastley commented 3 years ago

Chiming in to say me too, this has been happening for us since Thursday.

Any specific information I can pass on that can help?

rizkyfadillah commented 3 years ago

Same here. However, the build was successfully uploaded to Play Store.

Screen Shot 2021-01-25 at 10 08 21
ndbeyer commented 3 years ago

Same here

adebree commented 3 years ago

@bitce Any news on this? Maybe the step can be adjusted so the editing of the details is not performed since uploading the artifact itself is working.

billnbell commented 3 years ago

Status? It has been almost a week.

bitce commented 3 years ago

Hey everyone!

There is no documentation/communication from Google about this change that would cause this, so we've reached out to them, hoping we can address this soon.

In the meanwhile, while this is still an alarming problem, deployments should still succeed despite the failing step/builds.

duy-ng-12354 commented 3 years ago

Same here. the app is deployed successfully but we cannot be comfortable with a 'red' build.

image

Please help to address this issue.

Thanks a lot.

Today, it works on my side without any changes.

adebree commented 3 years ago

I have the same observation, it started to work again on our projects without changes from our side.

ndbeyer commented 3 years ago

Seems to work again

bitce commented 3 years ago

We can no longer reproduce the issue either, so this should be working from now on!