Search Issue Tracker

Won't Fix

Votes

0

Found in

2020.3.41f1

2021.3.12f1

2022.1.20f1

2022.2.0b12

2023.1.0a15

2023.2.0a1

Issue ID

UUM-17062

Regression

No

[Android] "Execution failed for task ':launcher:assetPackDebugPreBundleTask'" after building AAB when multiple Android asset pack names end the same

--

-

Possibly Google bug: [https://partnerissuetracker.corp.google.com/issues/255732500]

Wait for news there.

 

How to reproduce:
1. Open the user’s attached “AndroidProj.zip“ project
2. In the Assets > AndroidPacks see that folders are named “Pack1.androidpack“ and “NewPack1.androidpack“
3. See that “Build App Bundle (Google Play)“ is checked in the Android Build Settings
4. Build for Android

Expected result: ABB is built successfully
Actual result: Build fails with “Execution failed for task ':launcher:assetPackDebugPreBundleTask'.“

Reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b12, 2023.1.0a15

Tested with: Windows 10

Note: not reproducible if folders are named differently (e.g. “Pack1.androidpack“ and “Pack2.androidpack“)

Full error message:
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':launcher:assetPackDebugPreBundleTask'.
> Multiple task action failures occurred:
> A failure occurred while executing com.android.build.gradle.internal.tasks.AssetPackPreBundleTaskRunnable
> C:\Users\deividas.balinskis\Downloads\IN-15663_AndroidProj (2)2023\Library\Bee\Android\Prj\Mono2x\Gradle\newtest\src\main\assets
> A failure occurred while executing com.android.build.gradle.internal.tasks.AssetPackPreBundleTaskRunnable
> Illegal char <:> at index 127: C:\Users\deividas.balinskis\Downloads\IN-15663_AndroidProj (2)2023\Library\Bee\Android\Prj\Mono2x\Gradle\test\src\main\assets;C:\Users\deividas.balinskis\Downloads\IN-15663_AndroidProj (2)2023\Library\Bee\Android\Prj\Mono2x\Gradle\newtest\src\main\assets
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at [https://help.gradle.org|https://help.gradle.org/]

  1. Resolution Note:

    Thank you for your bug report.

    After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.

    The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.