I am experiencing an issue with an assembly definition that uses the FMod plugin. When the Unity Addressables library is present, a class that utilizes the FMod class with the dependency will throw an error about missing a dependency. The only solve is to add the dependency to the asmdef that does not need it.
This may be normal. FMOD may be programmed in such a way that it detects the presence of the Addressables package and if so, enables its own code that supports loading from Addressables. Therefore any code using FMOD will also have to add a dependency to Addressables.
You can check the FMOD source code to see if that is really the case. There’s probably some #if ADDRESSABLES_PACKAGE_PRESENT conditional in their code (the identifier is just an example).
Yes, your thinking there is correct, if Fmod was embedded in the assembly throwing the error. The issue is FMod has its own asmdef that does include the reference to addressables. The expected behavior here is that an assembly referencing FMod can use any code in the FMod plugin(as long as it isnt a direct call to addressables) without having to change the assembly definition. Like the screenshots show, there isnt a direct reference to addressables in this file, therefore the dependency should not be needed.
