SUPERCILEX
commented
3 years ago The credentials lambda is probably capturing the build file scope. Try this: serviceAccountCredentials.set(file("<path-to-credentials.json>")).
Closed anthonymonori closed 3 years ago
SUPERCILEX
commented
3 years ago The credentials lambda is probably capturing the build file scope. Try this: serviceAccountCredentials.set(file("<path-to-credentials.json>")).
anthonymonori
commented
3 years ago Thanks, that was it! Honestly overlooked that, and it seemed to work until we upgraded both GPP and Gradle. Unsure what changed, but I suspect it was nothing to do with GPP and was rather a change on Gradle's side that triggered it.
Thanks for the help 🙇
SUPERCILEX
commented
3 years ago Yeah, probs a bug. 🤷♂️
pfieffer
commented
1 year ago For me upgrading the gradle play publisher to 4.0.0 did the trick
app: build.gradle
plugins {
- id("com.github.triplet.play") version "3.8.1"
+ id("com.github.triplet.play")
}project: build.gradle
repositories {
google()
mavenCentral()
+ maven { url 'https://oss.sonatype.org/content/repositories/snapshots' }
}
buildscript {
- classpath("com.google.apis:google-api-services-androidpublisher:v3-rev142-1.25.0")
+ classpath 'com.github.triplet.gradle:play-publisher:4.0.0-SNAPSHOT'
}
Describe the bug
After upgrading to Gradle 7.1.1 and Play Publisher Plugin 3.6.0 we have encountered an error during the
:<app>:publish<Variant>Bundletask. We publish multiple (3) apps from the same repo, and all the some work as before, but one of them in particular fails during thecommitEditFortask.All the configuration we have on that specific app's gradle file is:
How To Reproduce
Versions
Tasks executed
./gradlew :<app>:publish<Variant>BundleExpected behavior
Before the upgrade to Gradle 7.1.1 and the latest AGP (3.6.0) the task simply succeeded with:
Additional context (if a crash, provide stack trace)
Stacktrace
``` FAILURE: Build completed with 2 failures. 1: Task failed with an exception. ----------- * What went wrong: Execution failed for task ':