When my app is submitted to the App Store, an error occurs The naming convention for 'NlOBase64 'is incorrect about swift-nio

[Lukasa]

Thanks for filing this. We've seen reports of this in some other packages, we'll take a look.

[ximlu]

Could you please clarify what you mean in your previous message? It appears to be written in Chinese characters. If you can provide a translation or more context, I would be happy to assist you.

[sjustfly]

@Lukasa I also encountered the same problem. Is there any solution

[colbrew]

We are getting something similiar in our CI pipeline:

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 '_NIODataStructures' from project 'swift-nio')

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 '_NIOBase64' from project 'swift-nio')

[Lukasa]

A quick update here: this appears to be related to Xcode's solving for the "diamond dependency problem". In some cases, Xcode will instruct SwiftPM to pull a package dependency out to a dynamic framework, instead of statically linking it. This will be done when it is necessary to avoid duplicate symbols appearing in your final product.

It looks like there is an Xcode bug where the resulting framework has an invalid bundle identifier. As this bundle identifier was generated by Xcode, this is fundamentally an Xcode issue. Can I ask you to file a report using Feedback Assistant?

We can also consider whether we should remove the underscores from the target names here, but you will find this across the package ecosystem. It's probably better that we don't play whack-a-mole with this, and instead get Xcode to understand that target names are not necessarily valid bundle identifiers.

[colbrew]

Thanks for the update Cory. Agree this sounds like an Xcode bug, I will file a bug report. For our team this is just a "mucking up the logs" issue; thanks again for taking a look.

[colbrew]

Submitted feedback - FB13704644

Demo of issue: https://github.com/colbrew/SwiftNIOBundleIDWarning