CFBundleIdentifier Fixer - 1 Year Subscription - [Cancel Anytime]:
CFBundleIdentifier Fixer - Prevents CFBundleIdentifier collision errors.
Why would you need to fix CFBundleIdentifier values in plist files?
Some development environments (including: LiveCode, Unity, Xamarin and Unreal Engine) build apps which include standard library bundles within the app. These bundles contain plist files having their own individual CFBundleIdentifier values. However the macOS app store requires CFBundleIdentifier values to be unique across all of the apps which have been added to the store by any developer. Otherwise you will get the CFBundleIdentifier Collision error from the Apple Transporter app.
How to Fix?
The solution is straightforward, just use the CFBundleIdentifier for the main app as a prefix for the CFBundleIdentifier values within each enclosed bundle plist file.
It is tedious to make these changes manually every time you build an app. CFBundleIdentifier Fixer makes the process as simple as dragging and dropping the new app. The application is traversed looking for all enclosed bundles and the associated plist files are automatically updated. If you accidentally drag & drop the app more than once, this situation is detected and the "Already updated" note will be written into the results field for each bundle.
How to use:
1) Launch the CFBundleIdentifier Fixer app.
2) Drag & Drop the app you want to fix onto the APP icon button.
3) The embedded bundle plist files will be updated and the results displayed in the Results field.
4) After fixing the CFBundleIdentifiers within an app, your app will need to be digitally signed. You may use command line commands or automated tools like App Wrapper to perform this signing.
Single User License.