Gradle Play Publisher 3.4.0

Note: This release is only compatible with the Android Gradle Plugin v4.1.x. See GPP v3.4.0-agp4.2 or v3.4.0-agp7.0 for a release compatible with the Android Gradle Plugin v4.2.x or v7.0.x respectively.

Improvements

• Credentials are now validated lazily. This means you don't have to specify credentials unless you are using a publishing task.
• ⚠️ The internal sharing output file name has changed to support split APKs. Instead of being [timestamp].json, the name is now [apk-file-name].json.

Gradle Play Publisher 3.4.0-agp4.2

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

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.