Null Reference Exception on Builds related to Initialize

Unity
1

Hi there, we are on Unity fmod version 2.02.24 and we are having issues with FMOD on our builds but not in the editor. No idea what to do to solve it as the builds dont show us line numbers that are useful for debugging. This doesnt seem to occur on every build and occurs rather sporadically, sometimes even if you rebuild the same project. We are using a separate machine to perform our builds but have reports of the same thing occurring when building directly from the Unity Editor.

NullReferenceException: Object reference not set to an instance of an object.
  at FMODUnity.RuntimeManager.Initialize () [0x00000] in <00000000000000000000000000000000>:0 
  at FMODUnity.RuntimeManager.get_Instance () [0x00000] in <00000000000000000000000000000000>:0 
  at FMODUnity.RuntimeManager.get_StudioSystem () [0x00000] in <00000000000000000000000000000000>:0 
  at FMODUnity.StudioListener.AddListener (FMODUnity.StudioListener listener) [0x00000] in <00000000000000000000000000000000>:0 
  at FMODUnity.StudioListener.OnEnable () [0x00000] in <00000000000000000000000000000000>:0 
Rethrow as SystemNotInitializedException: [FMOD] Initialization failed
  at FMODUnity.RuntimeManager.get_Instance () [0x00000] in <00000000000000000000000000000000>:0 
  at FMODUnity.RuntimeManager.SetListenerLocation (System.Int32 listenerIndex, UnityEngine.GameObject gameObject, UnityEngine.GameObject attenuationObject) [0x00000] in <00000000000000000000000000000000>:0 
  at FMODUnity.StudioListener.Update () [0x00000] in <00000000000000000000000000000000>:0
2

You’re right about the log not being too useful, is there anything else in the logs that could help figure out the cause?
Are you able to get any more information from the exception if you use a more verbose logging level?

3

Unfortunately, changing the logging level didn’t help the issue. But we found a fix, it seems that during the build process sometimes the settings file’s platforms aren’t recognized. This happened after an upgrade of FMOD minor version. Deleting and recreating the settings file seems to have done the trick which makes me think that maybe in a previous version the internal scriptable objects for the platforms weren’t managed correctly. Our team had a similar issue with internal SOs (Unity bug that may be fixed in a later version) in the past and tend to avoid them.