Unable to create release build

[Gerrel]

Summary

Get a error for release builds in the device logs "DYLD, Library not loaded: openssl.dylib, Reason: unsafe use of relative rpath openssl.dylib"

Steps to reproduce

Create a release build with the Demo project and install on device.

What is the current bug behavior?

App does not want to start.

What is the expected correct behavior?

App works like debug builds

Relevant logs and/or screenshots

Possible fixes suggested remediation

[kokitang]

I tried to build in release env, and it works.

For a potential issue maybe relative:
Try to edit your signing cert in KeyChain.

From:

To:

[kokitang]

Or just give a try to re-download & re-build the project.

[kokitang]

However, I want to ask you an off-topic question. Have you make any successful connection to demo's VPN in debug build?

[Gerrel]

Hmm..ok. Will give it another try tomorrow.
I’ve not tested the demo’s vpn, but replaced it with my own openvpn server configurations. I have two vpn servers and it works on one, but still figuring out why it not working on the other.

[keeshux]

@Gerrel for connectivity problems open a new issue, AFAICT this is unrelated for being a linking error.

Honestly I never faced that error. I suggest you first remove the project derived data under ~/Library/Developer/Xcode/DerivedData/ and see if something changes. Xcode can often be obscure and unpredictable.

[Gerrel]

• will check it on a another Mac that still runs High Sierra (over 2 weeks)

[Gerrel]

Solution: In the build settings you need to set "Enable Bitcode" to No.

[keeshux]

Thanks for the hint, it's worth a mention in the README.