krzyzanowskim/OpenSSL

[RunTime Error] /usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file)(1.1.1700)

SunXiaoShan opened this issue · 2 comments

SunXiaoShan commented

Hi,

I have upgraded from 1.1.1500 to 1.1.1700 recently. The build code is good but it will get a crash when I running.
By the way, it works well on v1.1.1500. Does any one have an idea for this ticket? Please help this, thanks.

mac os: 12.4 (21F79)
XCode: 13.4 (13F17a)
Mobile: iPhone 11 pro
iOS: 15.5
pod version: 1.11.3

dyld[5259]: Library not loaded: @rpath/OpenSSL.framework/OpenSSL Referenced from: /private/var/containers/Bundle/Application/OOOOOOOO-XXXX-OOOO-XXXX-OOOOOOOOOOOO/AAAAA.app/AAAAA Reason: tried: '/usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file), '/private/var/containers/Bundle/Application/OOOOOOOO-XXXX-OOOO-XXXX-OOOOOOOOOOOO/AAAAA.app/Frameworks/OpenSSL.framework/OpenSSL' (no such file), '/usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file), '/private/var/containers/Bundle/Application/OOOOOOOO-XXXX-OOOO-XXXX-OOOOOOOOOOOO/AAAAA.app/Frameworks/OpenSSL.framework/OpenSSL' (no such file), '/System/Library/Frameworks/OpenSSL.framework/OpenSSL' (no such file) Library not loaded: @rpath/OpenSSL.framework/OpenSSL Referenced from: /private/var/containers/Bundle/Application/OOOOOOOO-XXXX-OOOO-XXXX-OOOOOOOOOOOO/AAAAA.app/AAAAA Reason: tried: '/usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file), '/private/var/containers/Bundle/Application/OOOOOOOO-XXXX-OOOO-XXXX-OOOOOOOOOOOO/AAAAA.app/Frameworks/OpenSSL.framework/OpenSSL' (no such file), '/usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file), '/private/var/containers/Bundle/Application/OOOOOOOO-XXXX-OOOO-XXXX-OOOOOOOOOOOO/AAAAA.app/Frameworks/OpenSSL.framework/OpenSSL' (no such file), '/System/Library/Frameworks/OpenSSL.framework/OpenSSL' (no such file)

krzyzanowskim commented

Library not loaded: @rpath/OpenSSL.framework/OpenSSL

It looks like the app does not embed the framework in the app bundle. There may be many reasons. It's an Xcode build setting.

burakCokyildirim commented

I took same error. I returned the 1.1.1500 version then its fixed.
I think, 1.1.1700 build has a problem. @krzyzanowskim