Skip to content
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

CFBundleIdentifier invalid characters #9912

Open
yutaabe200 opened this issue Jun 15, 2022 · 12 comments
Open

CFBundleIdentifier invalid characters #9912

yutaabe200 opened this issue Jun 15, 2022 · 12 comments

Comments

@yutaabe200
Copy link

@yutaabe200 yutaabe200 commented Jun 15, 2022

Step 1: Describe your environment

Xcode version 13.3.1
Firebase SDK version: 9.1.0
Installation method: Swift Package Manager
Firebase Component: Firestore, Analytics, Auth, Storage, Messaging, Installations
Target platform(s): iOS

Step 2: Describe the problem

I get the following error when uploading to App Store connect.

This bundle is invalid. The bundle at path Payload/Test.app/Frameworks/GoogleUtilities_Environment.framework has an invalid 
CFBundleIdentifier 'GoogleUtilities_Environment' There are invalid characters(characters that are not dots, hyphen and 
alphanumerics) that have been replaced with their code point 'GoogleUtilities\u005fEnvironment' CFBundleIdentifier must be 
present, must contain only alphanumerics, dots, hyphens and must not end with a dot. [see the Core Foundation Keys at 
https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.
html#//apple_ref/doc/uid/TP40009249-102070-TPXREF105]
This bundle is invalid. The bundle at path Payload/Test.app/Frameworks/GoogleUtilities_Logger.framework has an invalid 
CFBundleIdentifier 'GoogleUtilities_Logger' There are invalid characters(characters that are not dots, hyphen and alphanumerics) 
that have been replaced with their code point 'GoogleUtilities\u005fLogger' CFBundleIdentifier must be present, must contain only 
alphanumerics, dots, hyphens and must not end with a dot. [see the Core Foundation Keys at 
https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.
html#//apple_ref/doc/uid/TP40009249-102070-TPXREF105]
@google-oss-bot
Copy link

@google-oss-bot google-oss-bot commented Jun 15, 2022

I found a few problems with this issue:

  • I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
  • This issue does not seem to follow the issue template. Make sure you provide all the required information.

@paulb777
Copy link
Member

@paulb777 paulb777 commented Jun 15, 2022

Sorry about the trouble and thanks for the report.

Please share the Xcode version being used as well.

@paulb777
Copy link
Member

@paulb777 paulb777 commented Jun 15, 2022

Thanks. This looks like an issue between Swift Package Manager and the App Store. SPM should not generate symbols that the App Store does not allow. We may need to follow up on Apple on this one.

Another option may be to remove the underscores from the GoogleUtilities package.

@yutaabe200
Copy link
Author

@yutaabe200 yutaabe200 commented Jun 15, 2022

@paulb777
Copy link
Member

@paulb777 paulb777 commented Jun 15, 2022

Strange that google/GoogleSignIn-iOS#124 was first reported on April 21st, but today is only report since. Based on those stats, it seems like there may be something particular about the specific project configuration.

Does updating to Xcode 13.4.1 make a difference?

@yutaabe200
Copy link
Author

@yutaabe200 yutaabe200 commented Jun 15, 2022

I'm having trouble with the exact same thing with Xcode 13.4.1...

@paulb777
Copy link
Member

@paulb777 paulb777 commented Jun 15, 2022

Added a question at https://developer.apple.com/forums/thread/704934?login=true&page=1#717415022

@jackgmarch
Copy link

@jackgmarch jackgmarch commented Jun 22, 2022

@paulb777 Hopefully I can reproduce the issue for a demo app soon so we can identify why this only occurs for some apps, but in the mean time it would be great if the change to remove underscores could be made on your side too, given Apple says underscores are disallowed in that thread and in the rejection reason.

@jackgmarch
Copy link

@jackgmarch jackgmarch commented Jun 22, 2022

@paulb777 We're linking Firebase Analytics/Crashlytics to a framework target, similar to the person in this thread https://bytemeta.vip/index.php/repo/google/GoogleSignIn-iOS/issues/124 who had the issue. Fixing this on our end would require a lot of code changes, and I'm pretty sure it's a valid setup, so unfortunately probably our only realistic way out is for the underscores to be removed if this is the cause.

This issue only started occurring for us recently as we just started using Firebase as a dependency via SPM, before we used Carthage.

@paulb777
Copy link
Member

@paulb777 paulb777 commented Jun 22, 2022

Yep linking into a dynamic framework could explain the issue. Would you create a reproducible example and file an issue to https://github.com/apple/swift/issues/new?assignees=&labels=bug&template=bug_report.md&title= as requested at https://developer.apple.com/forums/thread/704934.

We'd like to hear a statement from Apple before making a breaking change in the Firebase support libraries.

@lugearma
Copy link

@lugearma lugearma commented Jun 27, 2022

I finally was able to solve this, I was linking Firebase into a dynamic framework so I removed the framework and linked it into my app target directly.

@paulb777 paulb777 added this to the Firebase 10 milestone Jul 19, 2022
@paulb777
Copy link
Member

@paulb777 paulb777 commented Jul 19, 2022

Marking for Firebase 10 to consider a GoogleUtilities breaking change release at the same time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants