We have a macOS app submitted to the mac app store which is built with Unity using FMOD. We are running into the following issue when trying to upload to the Mac App Store:
I read this to say that no two submissions on the Mac App Store can use the same CFBundleIdentifier, even for common plugins like FMOD.
We first ran into the issue about a year ago, and fixed it by manually modifying the fmodstudio.bundle's info.plist file to add a unique value to the end of the CFBundleIdentifier. This worked, and all was well.
We are running into the same issue again now when trying to submit an update. However, if we modify the plugin info.plist now, it is unable to load the plugin and so FMOD throws errors, resulting in no audio in the game. If we reset the info.plist value to default, the plugin loads fine and audio is all good, however we cannot submit to the app store because of the above validation issue.
Is there any way around this? Is it a mistake that no two applications are allowed to use the same plugins, or is the expected behaviour that everyone modifies the CFBundleIdentifier of any common plugins? What else do we need to do so that the plugins are not blocked / fail to load when we do modify the CFBundleIdentifier so that it passes the submission validation to the app store?
Code Block ERROR ITMS-90511: "CFBundleIdentifier Collision. The Info.plist CFBundleIdentifier value 'com.fmod.fmodstudio' of '<GAMENAME>.app/Contents/PlugIns/fmodstudio.bundle' is already in use by another application."
I read this to say that no two submissions on the Mac App Store can use the same CFBundleIdentifier, even for common plugins like FMOD.
We first ran into the issue about a year ago, and fixed it by manually modifying the fmodstudio.bundle's info.plist file to add a unique value to the end of the CFBundleIdentifier. This worked, and all was well.
We are running into the same issue again now when trying to submit an update. However, if we modify the plugin info.plist now, it is unable to load the plugin and so FMOD throws errors, resulting in no audio in the game. If we reset the info.plist value to default, the plugin loads fine and audio is all good, however we cannot submit to the app store because of the above validation issue.
Is there any way around this? Is it a mistake that no two applications are allowed to use the same plugins, or is the expected behaviour that everyone modifies the CFBundleIdentifier of any common plugins? What else do we need to do so that the plugins are not blocked / fail to load when we do modify the CFBundleIdentifier so that it passes the submission validation to the app store?
