# macOS fmodstudioL.bundle marked only for Intel CPUs **URL:** \ **Category:** Unity\ **Created:** [July 9, 2025, 5:23pm UTC](https://qa.fmod.com/t/macos-fmodstudiol-bundle-marked-only-for-intel-cpus/23136 "2025-07-09T17:23:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![SmileK2](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@SmileK2](https://qa.fmod.com/u/SmileK2)\ **Post date:** [July 9, 2025, 5:23pm UTC](https://qa.fmod.com/t/macos-fmodstudiol-bundle-marked-only-for-intel-cpus/23136/1 "2025-07-09T17:23:33Z")
I noticed that in FMOD for Unity 2.03.08 that “fmodstudioL.bundle” is marked for Intel 64-bit CPUs only, but the binary itself includes the arm64 architecture slice for Apple Silicon. The bundle itself is required for Apple Silicon development builds, but doesn’t get copied to the final .app unless it’s correctly marked (like the other macOS binaries) as compatible with all macOS architectures. ---
**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:** [July 11, 2025, 12:05am UTC](https://qa.fmod.com/t/macos-fmodstudiol-bundle-marked-only-for-intel-cpus/23136/2 "2025-07-11T00:05:03Z")
Hm, how are you determining that the bundle is marked for Intel 64-bit CPUs only? Has this been the case with previous FMOD versions too? ---
**Author:** ![SmileK2](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@SmileK2](https://qa.fmod.com/u/SmileK2)\ **Post date:** [July 11, 2025, 12:47am UTC](https://qa.fmod.com/t/macos-fmodstudiol-bundle-marked-only-for-intel-cpus/23136/3 "2025-07-11T00:47:36Z")
Yeah, it actually has been there since at least a version or two back. I just didn’t submit a bug report until it bit me twice. I verified this on a completely fresh local Unity project and did nothing more than import the FMOD package. Two of the three platform binaries for macOS are correctly marked as compatible with “Any CPU” while the fmodstudioL binary is only marked for “Intel 64-bit”. ![Screenshot 2025-07-10 at 5.45.41 PM](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/f/f0c82552c1804731b4bf01a89cbf672b16779920.png) ---
**Author:** ![zanval](https://avatars.discourse-cdn.com/v4/letter/z/c67d28/32.png) [@zanval](https://qa.fmod.com/u/zanval)\ **Post date:** [July 12, 2025, 1:12pm UTC](https://qa.fmod.com/t/macos-fmodstudiol-bundle-marked-only-for-intel-cpus/23136/4 "2025-07-12T13:12:14Z")
Just encountered this today, too. Setting it to Any CPU resolves the issues, but Build with FMod Live are broken “out of the box” due to this issue. ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [July 16, 2025, 10:54pm UTC](https://qa.fmod.com/t/macos-fmodstudiol-bundle-marked-only-for-intel-cpus/23136/5 "2025-07-16T22:54:06Z")
Hi, Thank you both for sharing the information and bringing this to our attention, I was able to reproduce the issue in **Unity 6000.1.0f1**. > [@SmileK2](#): > > I verified this on a completely fresh local Unity project and did nothing more than import the FMOD package. > [@zanval](#): > > Just encountered this today, too. > Setting it to Any CPU resolves the issues, but Build with FMod Live are broken “out of the box” due to this issue. Could I please confirm which Unity version you’re using? As a temporary workaround, downgrading to another Unity version might help. For example, during my testing, the issue did not occur in **Unity 6000.0.7f1** or **2022.3.x** on either Windows or macOS. I’ve passed this on to the dev team and will keep you updated with any progress. ---
**Author:** ![SmileK2](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@SmileK2](https://qa.fmod.com/u/SmileK2)\ **Post date:** [July 16, 2025, 11:12pm UTC](https://qa.fmod.com/t/macos-fmodstudiol-bundle-marked-only-for-intel-cpus/23136/6 "2025-07-16T23:12:53Z")
This is on Unity **6000.1.0f1**. The workaround is super simple on any version of Unity - just mark the offending binary as compatible with all CPUs on macOS and you’re good. We’re not blocked by this, I just thought it would be good to report it so future users don’t run into the same issue. ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [July 16, 2025, 11:18pm UTC](https://qa.fmod.com/t/macos-fmodstudiol-bundle-marked-only-for-intel-cpus/23136/7 "2025-07-16T23:18:35Z")
Thank you for confirming the Unity version and sharing the workaround. I’ll make sure to forward this to the dev team for further investigation.