Build error (bundle does not exist) when building Play Asset Delivery

Open

#54 opened on Aug 16, 2021 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: android, csharp, unity
Domain: build-system, mobile

Research direction

Reproduce the Play Asset Delivery build in Unity 2020.3.15f2 with Addressables 1.18.15 by selecting Build > New Build > Play Asset Delivery. Inspect the first addressable group using the Play Asset Delivery Provider, especially “FastFolowContent,” and verify the build completes without the missing mountainartstatic_assets_all.bundle error.

Written by the indexing model from the issue text.

Description

I'm receiving an error when building the Play Asset Delivery. My version of Addressables is at 1.18.15. I'm also using the exact Unity version (2020.3.15f2) that the sample uses. When I select Build > New Build > Play Asset Delivery, I receive this error:

Library/com.unity.addressables/aa/Android/Android/mountainartstatic_assets_all.bundle does not exist
UnityEditor.GenericMenu:CatchMenu (object,string[],int)
     
Addressable content build failure (duration : 0:00:00)
UnityEditor.GenericMenu:CatchMenu (object,string[],int)

It seems to occur on the first addressable group with "FastFolowContent". AlI of my groups have the Asset Bundle Provider set to use the “Play Asset Delivery Provider”. I tried a few different methods to fix this, such as setting different Bundle Naming Modes on that group, changing the compression method, shortening the name of the group, etc... This is what the offending group looks like.

Any ideas?

Dominant language: C#
Stars: 1.5k
Forks: 303
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.