Why would you need to fix CFBundleIdentifier values in plist files?

Some development environments (like LiveCode) 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. Otherwise you will get the error CFBundleIdentifier Collision 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 a new app. Therefore the CFBundleIdentifier Fixer app makes the process as simple as dragging and dropping the new app onto a button. The application is traversed looking for all enclosed bundles and the associated plist files are automatically updated.

If you accidentally drag & drop an app more than once, this situation is detected and the "Already updated" notice will be written into the results field for each enclosed bundle.

Note: After fixing the CFBundleIdentifiers within an app, your app will need to be digitally signed. You may use command line utilities or automated tools like App Wrapper to perform this signing.

App Privacy

The developer, .com Solutions Inc., indicated that the app’s privacy practices may include handling of data as described below. For more information, see the developer’s privacy policy.

Data Not Collected

The developer does not collect any data from this app.

Privacy practices may vary, for example, based on the features you use or your age. Learn More


  • Family Sharing

    With Family Sharing set up, up to six family members can use this app.