# ERROR ITMS-90511: CFBundleIdentifier Collision on FMOD bundles

**URL:** <https://qa.fmod.com/t/error-itms-90511-cfbundleidentifier-collision-on-fmod-bundles/16898>\
**Category:** Unity\
**Tags:** mac\
**Created:** [March 18, 2021, 6:25am UTC](https://qa.fmod.com/t/error-itms-90511-cfbundleidentifier-collision-on-fmod-bundles/16898 "2021-03-18T06:25:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bfskyle](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/bfskyle/32/257_2.png) [@bfskyle](https://qa.fmod.com/u/bfskyle)\
**Post date:** [March 19, 2021, 4:08am UTC](https://qa.fmod.com/t/error-itms-90511-cfbundleidentifier-collision-on-fmod-bundles/16898/2 "2021-03-19T04:08:03Z")

</div>

@mathew I think you might be able to shed some light here - saw a similar issue in another thread:

> [@MacOS DllNotFoundException: fmodstudioL](https://qa.fmod.com/t/macos-dllnotfoundexception-fmodstudiol/16452/24):
>
> Thank you so much for providing your .app, I was able to reproduce the issue here on my Mac. So the problem is actually due to a codesign validity check triggered because the FMOD bundle has been tampered with. The tampering is the line endings for the Info.plist file contained within fmodstudio.bundle and fmodstudioL.bundle. I was able to quickly fix it here by installing dos2unix via homebrew and running it on the file. We ship the Info.plist files with Unix style line endings as is the norm …

Here you mention that the dll was not found because the info.plist file was tampered with. In my case, it is intentionally being ‘tampered’ with because MacOS App Store requires a unique CFBundleIdentifier, so I am editing it to be unique. Any ideas on how I should be approaching this?

---

_[View the full topic](https://qa.fmod.com/t/error-itms-90511-cfbundleidentifier-collision-on-fmod-bundles/16898)._