error framework not found openssl after update to GRPC 1.15.1 & BoringSSL 0.0.2
#16821
Comments
|
I have the same issue |
|
@sibinlu @petard - what are the names of the pods that you are using? The reason was likely those pods you used were using BoringSSL that gRPC depended on, but they did not explicitly specify the dependency in their podspec. We recently renamed the BoringSSL lib to avoid conflict with other openssl libraries, which can cause issue in this case. |
|
From my pod file: and the Locking the pod to |
|
@petard - thanks. And can you tell us which line did you fail on? I tried building |
|
@muxi Im using this sdk. https://github.com/tokenio/sdk-objc |
|
@sibinlu - Sorry I actually meant archiving was ok on my side. Let me try your sdk. |
|
@sibinlu - I also passed archiving tokensdk. I wonder if you have any |
|
Hey @muxi , we don't have any The good news is that you remind me to check the xcode project file and I find that there is a setting My theory is that if you have worked with earlier version boringSSL, your project will explicitly have the openssl framework setting. Even after you update to the new version, for some reason the flag hasn't been changed. That explain why muxi don't have that issue on a new project. If you have linked an earlier version BoringSSL (in my case that's TokenSdk 1.0.99) then switch to the newest version , you will suffer that problem. @petard Hope this works for you too. |
|
That makes sense. Thanks for the idea @sibinlu. By |
|
I did it manually. |
|
@sibinlu Awesome, changing the framework name to |
What version of gRPC and what language are you using?
Objective-C Swift3
GRPC 1.15.1
BoringSSL 0.0.2
What operating system (Linux, Windows, …) and version?
Xcode 10.0
What did you do?
I use cocoapod to install a sdk (TokenSdk) which depends on GRPC. everything is all right before 1.15.1 release. After GRPC update to 1.15.1, an error
ld: framework not found opensslwill be throw when I want to archive my project.
Currently I add
pod 'BoringSSL-GRPC', '0.0.1'to avoid the pod update.Podfile:
project 'Token', 'BetaDebug' => :debug, 'BetaAdhoc' => :release
def common_pods
source 'https://github.com/CocoaPods/Specs.git'
source 'https://github.com/tokenio/token-cocoa-pods.git'
pod 'CocoaLumberjack/Swift'
pod 'AFNetworking''
pod 'Fabric'
pod 'TokenSdk'
pod 'Crashlytics'
pod 'RealmSwift', '3.1.0'
pod 'Localize-Swift'
#pod 'RealmSwift', :git => 'https://github.com/realm/realm-cocoa.git', :submodules => true
#pod 'Realm', :git => 'https://github.com/realm/realm-cocoa.git', :submodules => true
pod 'Bolts-Swift'
pod 'Alamofire'
pod 'CountryPicker'
pod 'BugfenderSDK/ObjC'
pod 'Firebase/Messaging'
pod 'Firebase/Core'
pod 'BoringSSL-GRPC', '0.0.1'
end
What did you expect to see?
Archive successfully
What did you see instead?
ld: framework not found opensslAny idea why this happens?
The text was updated successfully, but these errors were encountered: