You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this package with Carthage.
When I archive and validate my app, I get an "Invalid Code Signature Identifier" error.
As I investigated, I found that if the framework has no dot characters in its bundle identifier, Xcode appends auto-generated string to signing identifier.
And this causes the "Invalid Code Signature Identifier" error.
sindresorhus/KeyboardShortcuts seems to have the same problem, so I'd recommend prepending com.sindresorhus. or something to their bundle identifier.
My environment:
macOS 10.15.5
Xcode 11.5
The text was updated successfully, but these errors were encountered:
nek023
changed the title
Bundle identifier with no dot characters will cause "Invalid Code Signature Identifier" error
Bundle identifier without dot characters will cause "Invalid Code Signature Identifier" error
Jun 10, 2020
I'm using KeyboardShortcuts in production and not seeing this problem. The Xcode project was generated by Swift Package Manager, so I don't think the info there is incorrect. No one else has reported this either.
@sindresorhus
Sorry for the late reply.
It is still occurring in Xcode 12.3 with Carthage 0.36.0.
But there seems to be no other similar reports, I think I should investigate further in my environment.
Thank you.
Hi @sindresorhus, thank you for the nice product!
I'm using this package with Carthage.
When I archive and validate my app, I get an "Invalid Code Signature Identifier" error.
As I investigated, I found that if the framework has no dot characters in its bundle identifier, Xcode appends auto-generated string to signing identifier.
And this causes the "Invalid Code Signature Identifier" error.
sindresorhus/KeyboardShortcuts seems to have the same problem, so I'd recommend prepending
com.sindresorhus.
or something to their bundle identifier.My environment:
The text was updated successfully, but these errors were encountered: