XCode 11.1 always tries to sign plug-in

[kunz]

I get random signing errors when building our plugins with XCode 11. It looks like XCode tries to sign the plugin even without any “Signing Identity”.

XCode output:

Signing Identity:     "-"
/usr/bin/codesign --force --sign - --timestamp=none /PlugIn.component

Should i now provide a Signing Identity in Projucer or is it still recommended to sign the plugins by script?

[anthony-nicholls]

Someone else I know hit this with Xcode 11, I got them to role back to Xcode 10.3 and everything was fine.

[t0m]

Code signing identity should be explicitly set by Projucer

Hi… Since updating to Xcode 11, I’m getting build failures with: .app: resource fork, Finder information, or similar detritus not allowed Command /usr/bin/codesign failed with exit code 1 I’m not sure exactly what that’s referring to, but it exposes a related problem in that if I don’t set a code-signing identity in Projucer, it doesn’t add a CODE_SIGN_IDENTITY setting to the XCBuildConfiguration in the .pbxproj file. This causes Xcode to default to a setting of “Sign to run locally”. I b…