OSX codesigning problem with libssl.dylib

Unity Engine
,
1

My team is preparing for an OSX Unity app release, for distribution outside of the AppStore.

We are building on 2018.4.2.

I am working through the code-signing process, but cannot get past this error:

BUILD/LuminantMusic.app: errSecInternalComponent

In subcomponent: .../BUILD/Application.app/Contents/Frameworks/libssl.dylib

I am new to OSX code signing, but have run through various walkthroughs, resources and tools, including UNSH/Unity-Apple-Distribution-Workflow and Unity Entitlements Tool. Also rebuilds and variations on the above command that include linking the entitlements. I seem to keep hitting this libssl.dylib error.

Does anyone have insight to what I am missing? I appreciate any guidance.

Much Thanks All.

2

Iā€™m no expert, but I believe you need to (separately) code-sign the dylib, and then code-sign the app bundle that contains it.

1 Like
3

Thanks Joe (and for many other of your helpful posts here).

No luck specifically signing BUILD/Application.app/Contents/Frameworks/libssl.dylib

4

Followup : I kept tinkering with this, and got success after working thorough security lock-keychain and security unlock-keychain, as found on this page : How to Fix iOS Application Code Signing Error? | by Ceyhun Keklik | Medium

3 Likes
5

Hi

I am facing the same issue, any update on how this is fixed?
I did unlock the keychain

@bgroves_ce

Thanks
Sri

6

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate: file not in an order that can be processed (link edit information does not fill the __LINKEDIT segment):

is the error, i tried setting the export path as well

7

I am facing this issue only after prepping it for steam, if not I am able to codesign it