App store connect validation failed with CFBundleIdentifier Collision

Question

Created Jul ’25

Replies 3

Boosts 0

Participants 2

We have a client with an application that includes a main application, NSEs (Notification Service Extensions) as an extension, and framework1 embedded within the main application.

The NSEs also require framework1 as a dependency. When we embedded framework1 within the NSEs, the App Store Connect validation failed with the following error:

Validation failed (409) CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.test.xyz-LoggerUtility' under the iOS application 'test.app'. (ID: -----------)

We've observed an issue specifically when uploading to App Store Connect. We're able to debug and distribute the application without any problems using our enterprise distribution.

Answered by DTS Engineer in 850262022

This is iOS, right?

If so, you can’t embed frameworks within an NSE. On iOS, all frameworks must be at the top level. See Placing Content in a Bundle.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

Jul ’25

Recommended

This is iOS, right?

If so, you can’t embed frameworks within an NSE. On iOS, all frameworks must be at the top level. See Placing Content in a Bundle.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1

Answer 2

neha24 OP

Jul ’25

Thanks for the update, Yes it is for iOS . Trying to understand why enterprise and debug builds don't show the same complaint, especially when frameworks are embedded in the NSE .

0

Answer 3

DTS Engineer OP

Apple

Jul ’25

Accepted Answer

Trying to understand why enterprise and debug builds don't show the same complaint

I suspect that your NSE is actually loading the framework from MyApp.app/Frameworks rather than loading the copy embedded in the NSE. That’s the only way I can see this actually working, due to the way that iOS handles nested code.

Regardless, this quote from Placing Content in a Bundle applies:

If you put content in the wrong location, you may encounter hard-to-debug code signing and distribution problems. These problems aren’t always immediately obvious.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1