gradle-play-publisher: FAILED_PRECONDITION when running publish*Bundle

Describe the bug

{

 "code" : 400,

 "errors" : [ {

 "domain" : "global",

 "message" : "This Edit has been deleted.",

 "reason" : "failedPrecondition"

 } ],

 "message" : "This Edit has been deleted.",

 "status" : "FAILED_PRECONDITION"

}

How To Reproduce

Versions

  • Gradle Play Publisher: 2.8.0
  • Gradle Wrapper: 6.5.1
  • Android Gradle Plugin: 4.0.1

Tasks executed

What tasks did you run?

publish{BuildVariant}Bundle

Expected behavior

Success publishing

Additional context (if a crash, provide stack trace)

Add any other context about the problem here. If this bug is a crash, run the task with --stacktrace to get the full context.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 1
  • Comments: 16

Commits related to this issue

Most upvoted comments

Huh, I’ll look into it then since creating a tighter bound on when the edit is created would be nice.

The generate edit task is no more. 😃 I moved that logic to a build service which means an edit will be generated by the first task that needs it.

Note that these changes still won’t help much when using auto resolution since an edit is needed to get the latest version codes early on in the build.

I believe that this is not a bug since it is intended behavior, but it’s a nice feature request (postpone the generateEdit task to a later stage).

Also, according to what @SUPERCILEX said, ppl do run into this sometimes, maybe the solution is to just add a topic into the readme explaining that concurrent builds will cause one of them to fail.