Gradle-play-publisher: Publish all productFlavor

Created on 7 Jan 2016 · 6Comments · Source: Triple-T/gradle-play-publisher

I know

In case you are using product flavors you will get one of the above tasks for every flavor. E.g. publishApkPaidRelease or publishListingPaidRelease

But it will be nice if there was a task publishAllApksRelease to publish all apk for every flavor. (same for listing)

enhancement

Source

aat-antoine

Most helpful comment

This is what I use to update all my 70+ flavours.
It should give exactly the same result as pabliscos suggestion, but I can verify that mine works:

task updateBleedingEdge(group: 'util') << {}
updateBleedingEdge.dependsOn {
    tasks.findAll { it.name.startsWith('publishApk') }
}

d-lindahl on 29 Jun 2016

👍3 🎉1

All 6 comments

This should give you what you want ;)

task('publishAllApksRelease').dependsOn(tasks.findAll { it.name.startsWith("publishApk") })

pablisco on 20 Apr 2016

@pablisco don't work this method.
Anyone know what we need do?

siloebb on 3 May 2016

This is what I use to update all my 70+ flavours.
It should give exactly the same result as pabliscos suggestion, but I can verify that mine works:

task updateBleedingEdge(group: 'util') << {}
updateBleedingEdge.dependsOn {
    tasks.findAll { it.name.startsWith('publishApk') }
}

d-lindahl on 29 Jun 2016

👍3 🎉1

The above works great, but is there a way to ignore the below error (as its the latest version) and go to the next publishApk task?

com.google.api.client.googleapis.json.GoogleJsonResponseException: 403 Forbidden
{
"code" : 403,
"errors" : [ {
"domain" : "androidpublisher",
"message" : "APK specifies a version code that has already been used.",
"reason" : "apkUpgradeVersionConflict"
} ],
"message" : "APK specifies a version code that has already been used."
}

johnnyzen on 22 Jan 2017

Does the plugin support variations in listings/metadata depending on product flavour?
Say you want to have a different set of screenshots for free/premium flavours, or different descriptions.