# BUG: Fmod 1.10 and 1.09.10 not building in Unity Android

**URL:** <https://qa.fmod.com/t/bug-fmod-1-10-and-1-09-10-not-building-in-unity-android/13790>\
**Category:** Unity\
**Created:** [March 28, 2018, 9:46am UTC](https://qa.fmod.com/t/bug-fmod-1-10-and-1-09-10-not-building-in-unity-android/13790 "2018-03-28T09:46:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sourcetreehugger](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@sourcetreehugger](https://qa.fmod.com/u/sourcetreehugger)\
**Post date:** [March 28, 2018, 9:46am UTC](https://qa.fmod.com/t/bug-fmod-1-10-and-1-09-10-not-building-in-unity-android/13790/1 "2018-03-28T09:46:38Z")

</div>

The following error is generated when I build an Android project with fmod studio. This error is not produced in 1.09.04 so you can use that as an alternative in the meantime.

Assets/Plugins/FMOD/RuntimeManager.cs(576,29): error CS0120: An object reference is required to access non-static member `FMODUnity.RuntimeManager.loadedBankRegister(FMODUnity.RuntimeManager.LoadedBank, string, string, bool, FMOD.RESULT)’

Steps to reproduce:  
Download Fmod studio 1.10.XX  
Download Fmod Unity 1.10.XX  
Open fmod project  
Create 3D event, add audio clip with loop region, assign to master bank.  
Build for all platforms.

In Unity:  
Create new project  
Import integration 1.10.XX  
Assign fmod project  
Create event emitter and assign event  
Add studio listener to camera  
Switch platform to android  
Add scene to build path  
Build

---

<div class="post-metadata">

**Author:** ![BiggerCatStudio](https://avatars.discourse-cdn.com/v4/letter/b/f04885/32.png) [@BiggerCatStudio](https://qa.fmod.com/u/BiggerCatStudio)\
**Post date:** [March 29, 2018, 6:16pm UTC](https://qa.fmod.com/t/bug-fmod-1-10-and-1-09-10-not-building-in-unity-android/13790/2 "2018-03-29T18:16:46Z")

</div>

Edit: if you comment that line, Unity is building and build is working fine.

Same problem here, Unity2017.3.1f1.  
Assets/Plugins/FMOD/RuntimeManager.cs(576,29)…

I can’t 1.09.04 - console is informing me that the code is obsolete, when I change one obsolete line I got 25 next errors.

---

<div class="post-metadata">

**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\
**Post date:** [April 2, 2018, 11:17pm UTC](https://qa.fmod.com/t/bug-fmod-1-10-and-1-09-10-not-building-in-unity-android/13790/3 "2018-04-02T23:17:29Z")

</div>

This issue has been fixed for the next release, the change can be found on our github page:

> <https://github.com/fmod/UnityIntegration/commit/db2c90ed3bc8d17d9a2c069381d89678e63424f3>

The function should have been accessed through the ‘Instance’ of the RuntimeManager.  
`
Instance.loadedBankRegister(…
`

---

<div class="post-metadata">

**Author:** ![koprivajakub](https://avatars.discourse-cdn.com/v4/letter/k/7ea924/32.png) [@koprivajakub](https://qa.fmod.com/u/koprivajakub)\
**Post date:** [April 4, 2018, 7:12am UTC](https://qa.fmod.com/t/bug-fmod-1-10-and-1-09-10-not-building-in-unity-android/13790/4 "2018-04-04T07:12:49Z")

</div>

> [@](#):
>
> This issue has been fixed for the next release, the change can be found on our github page:  
> [Fixed load bank returning ERR\_INVALID\_HANDLE on Android. · fmod/fmod-for-unity@db2c90e · GitHub](https://github.com/fmod/UnityIntegration/commit/db2c90ed3bc8d17d9a2c069381d89678e63424f3)
> 
> The function should have been accessed through the ‘Instance’ of the RuntimeManager.  
> `
> Instance.loadedBankRegister(…
> `

This fix worked for me. Do you have any roadmap/date when this will be availabe in release?

---

<div class="post-metadata">

**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\
**Post date:** [April 5, 2018, 3:48am UTC](https://qa.fmod.com/t/bug-fmod-1-10-and-1-09-10-not-building-in-unity-android/13790/5 "2018-04-05T03:48:18Z")

</div>

This fix will be in the next release, due at the start of May.