Issue deploying to Google Play - HTTP response code 500

Question & Answer Builds
,
1

Hi, got an error deploying to Google Play and I cannot solve it. It does everything fine until the end.

Committing edit
Failed to commit edit, error: googleapi: got HTTP response code 500 with body: {
“error”: {
“code”: 500,
“message”: null
}
}

Bitrise shows the following log:

+------------------------------------------------------------------------------+
| (6) google-play-deploy@1.2.1                                                 |
+------------------------------------------------------------------------------+
| id: google-play-deploy                                                       |
| version: 1.2.1                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2017-04-14T18:47:41Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
INFO[18:47:41] Start installing (golang) with apt-get       
INFO[18:47:41]  * [OK] Step dependency (go) installed, available. 

Configs:
- JSONKeyPath: file://Goo***son
- PackageName: xx.xxxxxxxxxxxxxx.xxxxxxxxxx
- ApkPath: /bitrise/deploy/app-release-0.1.32-32-xxxxxxxx.apk
- Track: alpha
- UserFraction: 0.5
- WhatsnewsDir: whatsnew
Deprecated Configs:
- ServiceAccountEmail: 
- P12KeyPath: 
- UntrackBlockingVersions: false

Authenticateing
Authenticated client created

Create new edit
 editID: XXXXXXXXXXXXXXXXXXXX

Upload apks
 uploaded apk version: 32

Update track
 updated track: alpha
 assigned apk versions: [32]

Update listing
 updating recent changes for version: 32
 - language: es-ES

Validating edit
Edit is valid

Committing edit
Failed to commit edit, error: googleapi: got HTTP response code 500 with body: {
 "error": {
  "code": 500,
  "message": null
 }
}

|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | google-play-deploy@1.2.1 (exit code: 1)                       | 17 sec   |

Thanks in advance,
Mgarciate

2

Hi,

500 is “internal server error”, coming from the Google Play servers.
Can you please try it again?

3

Hi, I changed the track to Beta and it’s working properly now. So I need to check the new rollout and release system into Google Play and why the alpha track doesn’t accept the deploy. Thx!

1 Like
4

Well, the thing about the “500” http error code is that you can never know what went wrong. There’s no response from the google api, so it might be an input error, but it also can be just a server side error, in which case a simple retry with the exact same parameters might work.

In general it definitely worth a retry, and if that wouldn’t work you can try to experiment with changing things, and/or reporting the issue to the service (in this case Google Play), so that they can look into the error.

I’m glad to hear that, please let us know if we can help with anything! :wink:

5

I had a bad release created in Alpha which didn’t allow bitrise to set the new apk file. Even the alpha track is working fine right now.
@viktorbenei thank you very much for your explanation.

1 Like
6

Ahh, good catch! :wink:

All I wish for is that the google api would return any description of the issue, instead of just a “500 internal error”, that would help a lot :stuck_out_tongue:

1 Like
7

You’re right,

Failed to commit edit, error: googleapi: got HTTP response code 500 with body: {
“error”: {
“code”: 500,
“message”: null
}

is not enough.

1 Like