Bug (Case 1370485) Addressables 1.19.6 content build failure (key was not present in the dictionary)

Addressables 1.19.6 outputs a "content build failure" when creating a new AssetGroup and then building content.

Reproduce

1. Open attached project
2. Open "Window > Asset Management > Addressables > Groups"
3. Click "Build > New Build > Default Build Script"

Actual
Unity outputs "The given key was not present in the dictionary." and "Addressable content build failure (duration : 0:00:00)" errors.

Expected
No error. Content builds successfully.

 

I ran into the same issue and was like yup, I'm just gonna stick with an old version again. Disheartening to see that it does that on a very simple basic assetgroup.

 

QA was able to reproduce the issue, thumbs up!
https://issuetracker.unity3d.com/is...ure-error-thrown-when-building-new-assetgroup

 

The bug-report is marked as "Won't fix":
https://issuetracker.unity3d.com/is...ure-error-thrown-when-building-new-assetgroup

Not sure if the "Won't fix" is just a mistake though, because why wouldn't you want to fix it?

 

I have the same problem after upgrading to 1.19.6

 

hey @unity_krista, I've updated the Addressables package to version 1.19.18 and I'm still seeing this issue when trying to build content.

I saw you mentioned setting the custom build & load paths. I'm not sure if we're using them correctly, they're set as follows:
LocalBuildPath: [UnityEngine.AddressableAssets.Addressables.BuildPath]/[BuildTarget]
LocalLoadPath: {UnityEngine.AddressableAssets.Addressables.RuntimePath}/[BuildTarget]

We've successfully been using addressables with these values on version 1.18.19 for a while now. Please let me know if I'm doing something dumb or if these paths need to be changed for the new version, thanks


Edit: I think we may be experiencing a different issue. As previously stated, we're running 1.18.19 which has worked fine until I created some new addressable groups today. All the groups & schemas seem to match existing settings. Now when I attempt to build, we get the following message logged twice:

Code (CSharp):

1. Could not find a part of the path ""
2. UnityEditor.GenericMenu:CatchMenu (object,string[],int)

followed by the

Addressable content build failure (duration : 0:00:00)

error message.

 

@unity_krista
Apologies, I'm sure now that this is another bug. The problem only arises when I do the following:

1. Create a new addressables group
2. Set the group to Pack Separately
3. Add one particular texture that I've determined was causing the issue

Some notes:

• If I set the group to Pack Together instead of separately, the build completes without failure.
• Reimporting the problematic texture doesn't help, and there's nothing strange about its import settings. Even diffing the meta file to another working texture's meta file shows nothing weird.
• Removing all other groups in our main project (so the one problematic texture asset is the only addressable asset in the project) does not work either.
• I'm unable to create a minimum reproduction project - copying the problematic texture + meta, and the entire AddressableAssetsData folder to a new project doesn't reproduce the error; instead it builds as expected.

I'll continue trying to reproduce this error in another project so I can submit a bug report. In the mean time, do you know if this sounds like any known issues?

 

I'm getting the exact same issue. Other members in my team aren't getting the same problem, the only difference I can think of is that I'm on windows 11 and they are on windows 10.
Also they have cache server enabled where as I don't.

Hope this information might be of some use

 

@unity_krista @HugeWill I've created another forum post specifically for the issue I've found to avoid clogging this thread up.
https://forum.unity.com/threads/bui...ticular-assets-are-packed-separately.1241938/

 

Regarding the content build failure, I get this error quite often, but only if I have been working on other things prior to doing a build.

As a work around, I simply restart Unity and immediately try again. This works for me every time.

So it seems that there may be some corruption in the memory that develops while using Unity that prevents building addressables that can only be cleared by restarting the editor.