We are currently stuck with our “effects” trying to load in or reference a bundle that does not even exist.
Our groups are all setup to “pack separately” including the “effects” group. There is NO effects.bundle whatsoever. Nowhere!
However, when we try to load and instantiate e.g.
Addressables.LoadAssetAsync<GameObject>("Assets/Effects/Ability/slam.prefab");
it always throws an error askinng for “effects.bundle” which DOES NOT EXIST. It is never generated nor referenced… EVER.
Full error:
Exception encountered in operation Resource<IAssetBundleResource>(effects.bundle), status=Failed, result= : RemoteAssetBundleProvider unable to load from url https://PROJECT.client-api.unity3dusercontent.com/client_api/v1/buckets/BUCKET/release_by_badge/latest/entry_by_path/content/?path=/StandaloneWindows64/sprites_assets_assets/effects.bundle, result='HTTP/1.1 404 Not Found'.
UnityEngine.AsyncOperation:InvokeCompletionEvent()
There is no such thing…
Instead, the abilities/effects in this case have been packed separately into their respective folders one by one… exactly what we have setup!
And yes, we have cleaned build cache for addressables in editor multiple times
VERSION: Unity 2019.4.20/23f
Addressables: 1.16.19 (even tried the newer ones without luck)
Multiple Machines (Windows)
Multiple library re-imports
Re-downloads from source control
fresh installs etc
Okay so I was able to resolve this.
Apparently this solution fixes a lot of other related issues that have been reported throughout the forums so maybe give this one a try if you are struggling with behavior that cannot be explained.
First, backup/screenshot/whatever all of your Addressable settings including profiles, groups and so on. We are going to delete them ALL and set them up from scratch again. If you use version control then you might be able to recover them a bit more easily though
Then, DELETE the following folders:
- Library
- AddressableAssetsData
- any directory containing previously built packs
This will remove any secretly/hidden cached data from the project and most importantly the addressable system!
Only deleting the library folder DID NOT work for us!
Then, inside the AddressablesGroup window, click on the “generate” button (or similar)- this will generate the default addressable assets and settings again.
In our case we had the removed files in Git so we were able to restore the groups there automatically and adjust any missing settings.
It turns out that our previously used groups and packages had “lost” (???) their connection to the main addressable asset which we were able to see and verify in soure control.
Now after resetting the whole system and re-generating the default assets we were able to continue and our groups and implementations are now working as intended.
