Gradle-play-publisher: Breaking bundle file naming in AGP 3.5.0 alpha 04

Created on 16 Feb 2019  路  7Comments  路  Source: Triple-T/gradle-play-publisher

Describe the bug

Android Gradle Plugin 3.5.0-alpha04 changed bundle file names to include variant, similar to apks.

So what would previously be 'app.aab' is now 'app-release.aab' for 'release' variant

I suspected this was a bug all when AGP introduced bundles since the naming convention wasn't consistent with apks, sadly since they fixed it so late, it now breaks this plugin.

To Reproduce

Run publish task (using bundles):

  • What went wrong:
    A problem was found with the configuration of task ':app:publishReleaseBundle'.
    > File '../app/build/outputs/bundle/release/app.aab' specified for property 'bundle' does not exist.

Versions

  • Gradle Play Publisher: 2.1.0
  • Gradle Wrapper (if applicable): 5.2.1
  • Android Gradle Plugin (if applicable): 3.5.0-alpha04
bug bundle

Most helpful comment

Since v2.2.0 might be a ways away, I've decided to release a hotfix v2.1.1 release.

All 7 comments

Annoying bug, tried to help, will downgrade gradle version used until it's fixed elsewhere.

Yeah, sorry again for shutting the PR down so fast. 馃槦 Adding new configurations options is almost never the answer. 馃檪

Yeah I think the fact that google changed the path should not be exposed. Look for the file in the new path and fall back to the old way seems fine to me, and that piece of code can be deleted in the future.

No worries, I agree that's probably not the best approach. The first approach was to simply fix the bug by the if check (first commit). Just simply do the if check.

if the idea is to simply not have the option (completely agreed), should have just taken the first commit via cherry-pick or reverted the second commit. It at least solves the immediate issue without waiting on a more elegant solution. It's no worse then the already hard coded solution in code.

This will be fixed in v2.2.0.

Since v2.2.0 might be a ways away, I've decided to release a hotfix v2.1.1 release.

Was this page helpful?
0 / 5 - 0 ratings