I got this report and the stacktrace below:
"Some times when uploading apk’s (has happened 2 times now) the plugins thinks that upload failed.
It then says that "No changes were applied to the Google Play account» but when checking in Google Play console, all apk’s were uploaded and published!"
Essentially the Google Play Publishing API fails to respond in time, so we assume failure.
Unfortunately from my testing, I've seen this a few times — timeouts or HTTP 500 server errors — even although the changes may have been applied. The API is not the most reliable.
So we should handle this particular situation (i.e. a timeout while committing the edits) and inform the user that the build outcome is unknown.
Assigning uploaded APK(s) to alpha release track...
The alpha release track will now contain the APK(s): 10040, 20045, 30043, 40044, 50041, 60042
Upload failed: org.jenkinsci.plugins.googleplayandroidpublisher.PublisherApiException: java.net.SocketTimeoutException: Read timed out
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
... 11 more
- No changes were applied to the Google Play account
Build step 'Upload Android APK to Google Play' marked build as failure