# FMOD disappearing from menu bar + compiler error after switch platform to iOS

**URL:** <https://qa.fmod.com/t/fmod-disappearing-from-menu-bar-compiler-error-after-switch-platform-to-ios/14583>\
**Category:** Unity\
**Created:** [April 18, 2019, 5:52am UTC](https://qa.fmod.com/t/fmod-disappearing-from-menu-bar-compiler-error-after-switch-platform-to-ios/14583 "2019-04-18T05:52:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nc57](https://avatars.discourse-cdn.com/v4/letter/n/ed8c4c/32.png) [@nc57](https://qa.fmod.com/u/nc57)\
**Post date:** [April 18, 2019, 5:52am UTC](https://qa.fmod.com/t/fmod-disappearing-from-menu-bar-compiler-error-after-switch-platform-to-ios/14583/1 "2019-04-18T05:52:14Z")

</div>

Hello,

I’m on Unity 2018.3.6f1. I have FMOD 2.0 installed in my project and went into File \> Build Settings… and clicked “Switch Platform” for iOS. After doing so, I noticed that “FMOD” vanished from my menu bar.

My game also won’t play now—After clicking play I get a message that says “All compiler errors have to be fixed before you can enter playmode!” and an error message in the console that says “Assets/Plugins/FMOD/src/Runtime/RuntimeManager.cs(533,21): error CS0103: The name ‘lowlevelSystem’ does not exist in the current context”

To make sure this wasn’t just a quirk of my project, I created a new project built for iOS and installed the same FMOD package. The same issue occurred.

How do I fix this error?

(Also FYI I’m new to Unity and programming in general)

Thank you!

---

<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 22, 2019, 11:03pm UTC](https://qa.fmod.com/t/fmod-disappearing-from-menu-bar-compiler-error-after-switch-platform-to-ios/14583/2 "2019-04-22T23:03:36Z")

</div>

You will need to fix a couple lines of code:

> <https://github.com/fmod/UnityIntegration/pull/21/files>

This has already been fixed for the next release.