-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Play Release not publishing *.aab package, failed, reason: socket hang up #426
Comments
Hi @sshields00 thank you for reporting. Do you still experience this issue or was it temporary? It looks like a network error on Google's side. |
Hello, I am still unable to push from Azure to Google Play I have tried many times over the last 7 days. I know the *.aab package produced by the build is valid as I can publish this manually through the Google Play website. Thanks. |
@sshields00 While I was searching for similar issues, I found this: #152 (comment), which may be of help to you. Could you doublecheck the bundle path? |
Hi @aleksandrlevochkin , I did come across #152 (comment) before. So I did a belt and braces check by verifying the package exists in the location, the following is the YAML that shows the path of the bundle and also the corresponding task log.
Command line Task Log
Google Play Task Log
|
Hi @aleksandrlevochkin. |
Hi,
Having this issue publising my .aab package to Google Play Console. Not sure if this is a networking issue from the Azure end. I did find similar issue with the same error here, r0adkll/upload-google-play#202.
I can manually upload the aab package to Google Play and it is accepted, but subsequent builds from my Azure pipeline fail like this.
Further Detailed logging
I have a stackoverflow flow question here.
https://stackoverflow.com/questions/77912766/unable-to-publish-signed-aab-package-to-google-play-console-from-azure-pipelin
The text was updated successfully, but these errors were encountered: