Resonance Audio ERR_FILE_NOTFOUND

Hey there!

We’ve noticed an issue popping up in our app’s bugtracker. It seems that FMOD cannot initialize on certain older Android devices as loading the Resonance Audio plugin is resulting in an ERR_FILE_NOTFOUND error.

Here’s a list of devices we’ve seen this on:

  • Samsung Galaxy Tab E (SM-T561M)
  • Samsung Galaxy Grand Prime (SM-G530H)
  • Samsung Galaxy Core 2 (SM-G355M)
  • Samsung Galaxy Tab 3 10.1 (GT-P5200)

Obviously, the biggest thing we can see connecting these devices is the fact that they’re from the Samsung Galaxy range. They are all also older devices, announced/released between 2013 to 2015. Unfortunately we do not actually have access to these devices, so we are unsure whether we are able to investigate further. Has FMOD or anyone else encountered any issues like this in the past?

Unity: 2019.4.13f1
FMOD: 2.01.05

Stack trace:

SystemNotInitializedException [FMOD] Initialization failed : Loading plugin ‘resonanceaudio’ from ‘libresonanceaudio.so’ : ERR_FILE_NOTFOUND : File not found.
<00000000000000000000000000000000> FMODUnity.RuntimeManager.CheckInitResult(FMOD.RESULT result, System.String cause)
<00000000000000000000000000000000> System.Action2[T1,T2].Invoke(T1 arg1, T2 arg2) <00000000000000000000000000000000> FMODUnity.Platform.LoadDynamicPlugins(FMOD.System coreSystem, System.Action2[T1,T2] reportResult)
<00000000000000000000000000000000> FMODUnity.Platform.LoadPlugins(FMOD.System coreSystem, System.Action`2[T1,T2] reportResult)
<00000000000000000000000000000000> FMODUnity.RuntimeManager.Initialize()
<00000000000000000000000000000000> FMODUnity.RuntimeManager.get_Instance()
<00000000000000000000000000000000> FMODUnity.RuntimeManager.get_StudioSystem()
<00000000000000000000000000000000> FMODUnity.RuntimeManager.AddListener(FMODUnity.StudioListener listener)
<00000000000000000000000000000000> FMODUnity.StudioListener.OnEnable()

We haven’t seen any issues like this on Samsung Galaxy, but the CPU architecture on the devices you’ve listed are either armeabi-v7a or x86, perhaps this is because the published apk is arm64-v8a but the integration is still trying to find an armeabi-v7a resonance audio plugin? The fact it’s only Samsung Galaxy devices is suspicious though, and I would expect the application to fail sooner if it was an issue with architecture.
It might be worth trying to support multiple apks if this is happening with a large enough number of users.