# Fmodstudio.l.bundle is damaged (MacOS Catalina)

**URL:** <https://qa.fmod.com/t/fmodstudio-l-bundle-is-damaged-macos-catalina/20257>\
**Category:** Unity\
**Tags:** unity\
**Created:** [May 26, 2023, 12:49pm UTC](https://qa.fmod.com/t/fmodstudio-l-bundle-is-damaged-macos-catalina/20257 "2023-05-26T12:49:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![karthikx25](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/karthikx25/32/5054_2.png) [@karthikx25](https://qa.fmod.com/u/karthikx25)\
**Post date:** [May 26, 2023, 12:49pm UTC](https://qa.fmod.com/t/fmodstudio-l-bundle-is-damaged-macos-catalina/20257/1 "2023-05-26T12:49:21Z")

</div>

Hi everyone,

I’m trying to run a university project on Unity and upon opening the file I got this error “fmodstudiol.bundle” is damaged and cannot be opened.

Funny enough, I was able to open this project without any issues on another system running MacOS Mojave and on a separate Windows system. It looks like this is only happening on my system which runs MacOS Catalina.

I also read a thread on here **[fmodstudioL - macOS catalina ERROR PLEASE HELP](https://qa.fmod.com/t/fmodstudiol-macos-catalina-error-please-help/15592)**  
which mentioned whitelisting the fmodstudiol.bundle file - But this did not work for me.

Is there any way to resolve this on MacOS Catalina?

FMOD Version : 2.02.03  
Unity Version: 2022.1.13f1

---

<div class="post-metadata">

**Author:** ![Andrew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/andrew/32/261_2.png) [@Andrew](https://qa.fmod.com/u/Andrew)\
**Post date:** [June 1, 2023, 5:18am UTC](https://qa.fmod.com/t/fmodstudio-l-bundle-is-damaged-macos-catalina/20257/2 "2023-06-01T05:18:44Z")

</div>

Just want to confirm you were able to work around the issue by manually un-quarantining the bundle as you specified in the linked thread?

---

<div class="post-metadata">

**Author:** ![RoryWalker](https://avatars.discourse-cdn.com/v4/letter/r/87869e/32.png) [@RoryWalker](https://qa.fmod.com/u/RoryWalker)\
**Post date:** [June 21, 2023, 3:01pm UTC](https://qa.fmod.com/t/fmodstudio-l-bundle-is-damaged-macos-catalina/20257/3 "2023-06-21T15:01:13Z")

</div>

This error is still prevalent. I find many threads and forums where people claim that it is fixed or will be fixed in the next FMOD update, but I have just updated the game I use for teaching to Unity 2022 and FMOD 2.02.15, and when students download the game ZIP from the cloud, the problem is always there (Mac only I should add). The problem is not unique to Catalina, it is prevalent in the more recents OS versions.

The fix is very easy these days, simply run the FMOD for Unity install package and follow the suggested steps. But still it is annoying that the game cannot work immediately, and it scares and confuses many students from the get-go which is far from ideal.

Is it not possible to fix this permanently? It didn’t use to be a problem with much older versions of Unity and FMOD (and OSX!).

---

<div class="post-metadata">

**Author:** ![Andrew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/andrew/32/261_2.png) [@Andrew](https://qa.fmod.com/u/Andrew)\
**Post date:** [June 22, 2023, 1:25am UTC](https://qa.fmod.com/t/fmodstudio-l-bundle-is-damaged-macos-catalina/20257/4 "2023-06-22T01:25:15Z")

</div>

Definitive answer here :

> [@Distribution of FMOD Studio Libs on Catalina/Big Sur in Integration](https://qa.fmod.com/t/distribution-of-fmod-studio-libs-on-catalina-big-sur-in-integration/17283/9):
>
> We’ve got to the bottom of this issue for now. If you download a zip file from the internet or even a LAN (possibly containing a Unity project with the FMOD integration already installed) and open it using a program that uses the macOS system zip functions (e.g. by simply double-clicking the zip), macOS will apply the quarantine flag to any executables and shared libraries it finds as it extracts them. This means that if you transfer a Unity project that has the FMOD integration already install…

It’s true, it never used to be a problem with older versions of macOS but Apple keeps updating its security measures and introducing new safety requirements in macOS itself so it’s not something we, as the developers of FMOD, have the power to fix - it’s just how macOS is these days.

---

<div class="post-metadata">

**Author:** ![RoryWalker](https://avatars.discourse-cdn.com/v4/letter/r/87869e/32.png) [@RoryWalker](https://qa.fmod.com/u/RoryWalker)\
**Post date:** [June 22, 2023, 11:14am UTC](https://qa.fmod.com/t/fmodstudio-l-bundle-is-damaged-macos-catalina/20257/5 "2023-06-22T11:14:05Z")

</div>

Thanks for your reply, it make sense. I will look into getting students set up with a Repo.

---

<div class="post-metadata">

**Author:** ![RoryWalker](https://avatars.discourse-cdn.com/v4/letter/r/87869e/32.png) [@RoryWalker](https://qa.fmod.com/u/RoryWalker)\
**Post date:** [July 20, 2023, 10:00am UTC](https://qa.fmod.com/t/fmodstudio-l-bundle-is-damaged-macos-catalina/20257/6 "2023-07-20T10:00:42Z")

</div>

By the way I found a good workaround, use Disk Images to package and transport your project instead of ZIPs, then there’s no error.
