Gradle Play Publisher 3.3.0

Note: This release is only compatible with the Android Gradle Plugin v4.1.x. See GPP v3.3.0-agp4.2 for a release compatible with the Android Gradle Plugin v4.2.x.

New features

• Support for single package multi-bundle uploads is now available. This enables using custom artifact directories with seperate phone and wear app bundles.

Bug fixes

• ResolutionStrategy.IGNORE stopped worked due to external API changes. This is now fixed.

Behavior changes ⚠️

• The global publish task has been replaced with an identical publishApps task. This resolves conflicts with the maven-publish plugin that had no other solution.

Gradle Play Publisher 3.3.0-agp4.2

This release is identical to v3.3.0, except that it includes the necessary changes to be compatible with the Android Gradle Plugin v4.2.x and v7.0.x. Known bugs from 3.1.0-agp4.2 still apply.

Gradle Play Publisher 3.2.0

Note: This release is only compatible with the Android Gradle Plugin v4.1.x. See GPP v3.2.0-agp4.2 for a release compatible with the Android Gradle Plugin v4.2.x.

New features

• Flavor dimensions are now a supported configuration level in playConfigs. They override build types, but get overridden by product flavors.

Bug fixes

• Supported third-party plugins (like crashlytics) will no longer be invoked when using a pre-built custom artifact.

Gradle Play Publisher 3.2.0-agp4.2-2

Fix another incompatibility with AGP

Gradle Play Publisher 3.2.0-agp4.2

This release is identical to v3.2.0, except that it includes the necessary changes to be compatible with the Android Gradle Plugin v4.2.x and v7.0.x. Known bugs from 3.1.0-agp4.2 still apply.

Gradle Play Publisher 3.1.0-agp4.2-2

This release is identical to 3.1.0-agp4.2, but it is compatible with AGP 3.2 beta 3 and AGP 7 alpha 4.

Gradle Play Publisher 3.1.0

Note: This release is only compatible with the Android Gradle Plugin v4.1.x. See GPP v3.1.0-agp4.2 for a release compatible with the Android Gradle Plugin v4.2.x.

New features

• Native deobfuscation symbols are now uploaded alongside APKs.
• Pending API changes are now validated when skipping a commit, enabling dry run use cases with --no-commit.
• When using a custom artifact directory, mapping files can now be targeted to specific APKs. See the docs for more details.

Bug fixes

• Fixed a crash reading version codes with auto resolution on after a manual version bump was performed.
• Added integration with crash reporting plugins (Crashlytics and Bugsnag currently) to automatically run their upload tasks on publish.
• Mapping files are no longer uploaded when publishing an app bundle as the mapping file is already a part of the bundle.
• The time between an API edit being generated and committed is now shorter, minimizing the chance of getting an editDeleted error.

Gradle Play Publisher 3.1.0-agp4.2

This release is identical to v3.1.0, except that it includes the necessary changes to be compatible with the Android Gradle Plugin v4.2.x.

Known bugs (won't be fixed)

• Intercepting the updated version code when using auto resolution is broken.

Gradle Play Publisher 3.0.0

Note: Gradle 6.5 and the Android Gradle Plugin v4.1.0 are the new minimum requirements. GPP 2.x will not support AGP 4.1 or above.

New features

• Better compatibility with the maven-publish plugin. If present, GPP will now add its dependencies to the publish task.
• Proxy authentication courtesy of @wintermute766.

Bug fixes

• Fixed a critical issue where playConfigs would sometimes inadvertently overwrite each other.

Breaking changes

• All properties now use the Gradle Property API. Upgrade steps: change foo = blah to foo.set(blah). For more guidance, see the updated docs.
• The outputProcessor property has been removed. The same functionality can now be achieved using native AGP APIs.
• Support for PKCS12 credentials (aka .p12 files) has been removed along with the serviceAccountEmail property. Use JSON credentials instead.
• Deprecated task names have been removed.
• promo-graphics are no longer supported in the Publishing API and have been removed.

Behavior changes

Promote task

The promote task now handles its different configuration options more simply. Promotion needs a from track and a promote track. If the fromTrack isn't specified explicitly, the least stable release track will be used. If the promoteTrack isn't specified explicitly, it will be assumed that you want to do an in-place update so the resolved fromTrack will be used. Previously, the track property was involved in the computation of both other properties.

Gradle Play Publisher 2.8.0

• Support for authenticating GPP with an environment variable! See the docs.
• Support for in-app update priority.
• Fixed an incompatibility with Gradle 6.5.
• Fixed a crash publishing releases to a new track.
• Removed unnecessary warnings.

PS: this release uses a new publishing mechanism, so in theory you can use any of our modules directly (though this isn't officially supported).