Skip to content
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

Delivery retry does nothing after a server error #1157

Open
ojoNetgem opened this issue Jan 15, 2025 · 6 comments
Open

Delivery retry does nothing after a server error #1157

ojoNetgem opened this issue Jan 15, 2025 · 6 comments
Labels
bug Indicates an unexpected problem or unintended behavior waiting-for-reply Indicates that an issue or pull request needs more information

Comments

@ojoNetgem
Copy link

Describe the bug

I got an app on which I used publishReleaseBundle but it fails with a 503 on commit. Any other attempts does nothing.

$ ./gradlew :app:publishAppReleaseBundle
> Task :app:publishAppReleaseBundle
Starting App Bundle upload: /path/to/app/build/outputs/bundle/AppRelease/app.aab
Uploading App Bundle: 15% complete
Uploading App Bundle: 30% complete
Uploading App Bundle: 45% complete
Uploading App Bundle: 60% complete
Uploading App Bundle: 75% complete
Uploading App Bundle: 90% complete
> Task :commitEditForAppDotApp
Committing changes

> Task :commitEditForAppDotApp FAILED
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':commitEditForAppDotApp'.
> A failure occurred while executing com.github.triplet.gradle.play.tasks.CommitEdit$Committer
   > 503 Service Unavailable
     POST https://androidpublisher.googleapis.com/androidpublisher/v3/applications/app.app/edits/numbers:commit?changesNotSentForReview=false
     {
       "code": 503,
       "errors": [
         {
           "domain": "global",
           "message": "The service is currently unavailable.",
           "reason": "backendError"
         }
       ],
       "message": "The service is currently unavailable.",
       "status": "UNAVAILABLE"
     }
     
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 1m 59s

Then retry:

$ ./gradlew :app:publishAppReleaseBundle
BUILD SUCCESSFUL in 10s

How To Reproduce

Not able to reproduce the initial condition

Versions

  • Gradle Play Publisher: 3.12.1
  • Gradle Wrapper: 8.10.2
  • Android Gradle Plugin: 8.8.0
@ojoNetgem ojoNetgem added the bug Indicates an unexpected problem or unintended behavior label Jan 15, 2025
@SUPERCILEX
Copy link
Collaborator

Hmmm, I guess there's bad cache invalidation. Running clean will force it to retry.

@ojoNetgem
Copy link
Author

That's what I guess too. Any possibilities to re-run publish without this overkill clean command?

@SUPERCILEX
Copy link
Collaborator

There's some edit-id file we generate, I think deleting that will make it rerun.

Copy link

This issue has been automatically marked as stale because it has not had recent
activity. It will be closed if no further activity occurs. Thank you for your
contributions.

@github-actions github-actions bot added the waiting-for-reply Indicates that an issue or pull request needs more information label Jan 24, 2025
@ojoNetgem
Copy link
Author

Can you please elaborate? I'm not so familiar with gradle cache control.

@github-actions github-actions bot removed the waiting-for-reply Indicates that an issue or pull request needs more information label Jan 25, 2025
Copy link

github-actions bot commented Feb 1, 2025

This issue has been automatically marked as stale because it has not had recent
activity. It will be closed if no further activity occurs. Thank you for your
contributions.

@github-actions github-actions bot added the waiting-for-reply Indicates that an issue or pull request needs more information label Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior waiting-for-reply Indicates that an issue or pull request needs more information
Projects
None yet
Development

No branches or pull requests

2 participants