In my project, I decide to migrate to Addressables. I used to use Resources to load my assets before. So that, I replaced all Resources.LoadAsync to Addressables.LoadAssetAsync. And I ran onto a case, when this replacement makes my application completely broken.
The case is next:
I have remote assets and update catalog on application start to fetch new bundles.
I have an asset in resources folder: path/to/boss_icon. And load it with Addressables.LoadAssetAsync("path/to/boss_icon")
In a time I had deleted this icon, cooked new application, cooked new Addressables build and uploaded it to my server.
After this, path/to/boss_icon becomes not available in old builds where it is physically included in build. As I get, this happens, because path/to/boss_icon is not presented in the new catalog. If it is, it makes Addressables completely unusable for managing local assets.
Is there a way to not make local assets unavailable on catalog updates, or I need to migrate back to Resources?