The bundle at path Payload/MyApp.app/Frameworks/_CollectionsUtilities.framework has an invalid CFBundleIdentifier '_CollectionsUtilities'

[kimdv]

The bundle at path Payload/MyApp.app/Frameworks/_CollectionsUtilities.framework has an invalid CFBundleIdentifier '_CollectionsUtilities'

[lorentey]

@kimdv Yep, that's quite clear.

SwiftPM's Xcode integration should not ever generate invalid bundle identifiers -- so the cause is clearly a tooling bug. However, the only way we can resolve this without waiting for a tools update is to rename the module. That takes a little bit of coordination, but it's a straightforward change and it can ship in 1.1.1.

[kimdv]

Some more info from the CI

2024-02-22T19:51:05.1131850Z ▸ Processing empty-_CollectionsUtilities.plist
2024-02-22T19:51:05.1154810Z     invalid character in Bundle Identifier. This string must be a uniform type identifier (UTI) that contains only alphanumeric (A-Z,a-z,0-9), hyphen (-), and period (.) characters. (in target '_CollectionsUtilities' from project 'swift-collections')

[kimdv]

That's not ideal.

• What platform are you targeting?

We have iOS 14 as min target version.

• Can you step me through your build setup? In particular, did you do any custom configuration to have this package be built as a set of standalone frameworks, as opposed to directly linking it into the app executable?

We have added it to our Xcode project under the "Package Dependencies" tab.
In our app target we import "Collections" and in a framework target we import "OrderedCollections".

Does that help you @lorentey ? :D

[depth42]

I am running into the same problem. The culprit seems to be the underscore in the CFBundleIdentifier _CollectionUtilities which is put into the generated Info.plist. Underscores are forbidden in these identifiers. This even prevents uploading apps using this to App Store Connect. An upload results in an error.

I am using Xcode 15.3 under macOS 14.4 to build a macOS / iPad app.

[depth42]

I am seeing the same warning when doing a debug build. When uploading to App Store Connect, this turns into an error.

[kimdv]

@kimdv Hmm… is there any utility or tool I could run locally to confirm the bug in a demo app? Have you experimented with any workarounds so far?

We had one place where we imported Collections and one place where use Collections and one place OrderedCollections.
You need to upload an app to the AppStore to get this error.

In our app target we import "Collections" and in a framework target we import "OrderedCollections".

Did you experiment with depending on the entire Collections package in the framework target and then just having your app target depend on the framework (which exposes Collections)? Same problem?

We have one target using Collections, and I will assume it's the same as it imports OrderedCollections.

[depth42]

I've also just hit this problem trying to release to the AppStore. Is there any resolution or work around at the moment?

I‘ve forked the repository and removed the underscore. This got rid of the build warning and the App Store Connect upload error. You can add the Swift package from the following URL to work around the problem until Apple issues an official fix: https://github.com/projectwizards/swift-collections

[lorentey]

That's not ideal.

• What platform are you targeting?
• Can you step me through your build setup? In particular, did you do any custom configuration to have this package be built as a set of standalone frameworks, as opposed to directly linking it into the app executable?

[vanvoorden]

We have added it to our Xcode project under the "Package Dependencies" tab.

@kimdv Hmm… is there any utility or tool I could run locally to confirm the bug in a demo app? Have you experimented with any workarounds so far?

In our app target we import "Collections" and in a framework target we import "OrderedCollections".

Did you experiment with depending on the entire Collections package in the framework target and then just having your app target depend on the framework (which exposes Collections)? Same problem?

[lorentey]

I see a warning when I try reproducing this:

Module 'HeapModule' was not compiled with library evolution support; using it means binary compatibility for 'TestFramework' can't be guaranteed

@kimdv do you see this too? Are you doing anything to suppress this warning?

[ptliddle]

I've also just hit this problem trying to release to the AppStore. Is there any resolution or work around at the moment?