-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The bundle at path Payload/MyApp.app/Frameworks/_CollectionsUtilities.framework has an invalid CFBundleIdentifier '_CollectionsUtilities' #364
Comments
Some more info from the CI
|
That's not ideal.
|
We have iOS 14 as min target version.
We have added it to our Xcode project under the "Package Dependencies" tab. Does that help you @lorentey ? :D |
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. |
@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 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?
Did you experiment with depending on the entire |
I see a warning when I try reproducing this:
@kimdv do you see this too? Are you doing anything to suppress this warning? |
I am seeing the same warning when doing a debug build. When uploading to App Store Connect, this turns into an error. |
- Removed the __ prefix from the module name of __CollectionsUtilities and related files because it was preventing apps from being uploaded to App Store Connect. apple#364
We had one place where we imported Collections and one place where use Collections and one place OrderedCollections.
We have one target using Collections, and I will assume it's the same as it imports OrderedCollections. |
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 |
Wanted to add that we're encountering this same issue |
Information
Checklist
main
branch of this package.Steps to Reproduce
Replace this paragraph with an explanation of how to reproduce the incorrect behavior.
Include a simple code example, if possible.
Expected behavior
It should compile fine allow to be uploaded to AppStore
Actual behavior
When using 1.1.0 to upload our app to the AppStore we get the following error:
The app compiles fine
The text was updated successfully, but these errors were encountered: