Search Issue Tracker

Fixed in 2021.2.X

Fixed in 2019.4.X, 2020.3.X, 2021.1.X

Votes

37

Found in

2020.1.3f1

Issue ID

1272592

Regression

Yes

[Android] Build fails when there are 680 or more files in the Streaming Assets folder

Mobile

-

Reproduction steps:
1. Download and open the user-submitted project "BuildStreamingAssets2020.zip"
2. Build the project

Expected result: Build is successful
Actual result: Build fails

Reproduces on: 2020.1.0b14, 2020.1.6f1

Does not reproduce on: 2019.4.11f1, 2020.1.0b13, 2020.2.0a1, 2020.2.0b3

Error message:
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade

UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)

Notes:
Does not reproduce on iOS
____
This is a problem outside of Unity, reported to Android Studio:
https://partnerissuetracker.corp.google.com/issues/177236664

A workaround would be to use custom Gradle files and specify the file extensions. By default we specify few extensions and list all the files from streaming assets. Instead of listing streaming assets you can specify the file extensions. The downside with that is that all files with such extension will be uncompressed including those outside of streaming assets.

  1. Resolution Note (fix version 2021.2):

    Fixed in 2022.1.0a10

  2. Resolution Note (fix version 2021.2):

    Fixed in 2021.2.0b13

  3. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.9f1

  4. Resolution Note (fix version 2020.3):

    Fixed in 2020.3.13f1

  5. Resolution Note (fix version 2019.4):

    Fixed in: 2019.4.32f1

Log in to vote on this issue

Comments (28)

  1. a-chambriat

    Mar 26, 2021 13:21

    broken too in 2020.3.0f1 & 2020.3.1f1

  2. a-chambriat

    Mar 26, 2021 11:37

    Hello, is there a workaround ?

  3. bluefallskyC

    Mar 12, 2021 03:43

    Resolution Note not work

    my info log is here

    [LIFECYCLE] [class org.gradle.internal.buildevents.TaskExecutionLogger] > Task :launcher:processDebugResources
    [INFO] [org.gradle.api.Task] AAPT2 aapt2-3.6.0-6040484-osx Daemon #0: shutdown
    (...)
    [ERROR] [org.gradle.api.Task] AAPT2 aapt2-3.6.0-6040484-osx Daemon #0 Failed to shutdown within timeout

  4. nishikinohojo

    Mar 04, 2021 15:50

    I think this workaround doesn't work.

    I couldn't remove " unityStreamingAssets.tokenize(', ')" from
    noCompress = ['.ress', '.resource', '.obb'] + unityStreamingAssets.tokenize(', ')
    (https://forum.unity.com/threads/unityplayer-displaychanged-method-to-add-a-surface-as-an-additional-display.1023124/#post-6649711)

    And with unityStreamingAssets.tokenize(', '), the effect of adding file extensions like ".bundle" is invalidated.

    Did I miss something? This is serious problem. Come on, Unity!

  5. drallcom3

    Jan 22, 2021 05:10

    I have the same issue. Too many files in streaming assets and the build fails. If I delete most of them the build succeeds.

    2020.2.1f1

    I also can't access the /issues/177236664 link.
    No idea what's going on in there.

  6. korypse

    Dec 12, 2020 11:37

    I tested on several versions of unity to find the one that is causing the problem and it is version 2020.1.0f1

    2020.1.17f1: Build failed
    2020.1.0f1: Build failed
    2019.4.16f1: Build success

    Here the change log: https://unity3d.com/fr/unity/whats-new/2020.1.0
    It is probably a regression from this patch https://issuetracker.unity3d.com/issues/android-loading-assets-from-assetbundles-takes-significantly-more-time-when-the-project-is-built-as-an-aab

    I create a git repository to reproduce: https://github.com/agrobost/unity_issue_1272592

  7. korypse

    Dec 12, 2020 08:51

    I have the same problem with unity 2020.1.17f1 & 2020.2.0b14
    FAILURE: Build failed with an exception.

    * What went wrong:
    Execution failed for task ':launcher:processReleaseResources'.
    > A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
    > AAPT2 aapt2-3.6.0-6040484-windows Daemon #0: Unexpected error during link, attempting to stop daemon.
    This should not happen under normal circumstances, please file an issue if it does.

  8. korypse

    Dec 11, 2020 21:41

    Is there a workaround ?

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.

Latest issues

See all new issues