Theoretical Fix issue with BoringSSL-GRPC via update to the podspec #343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix to issue #342
Taking note from how Firebase uses
preserve_path
https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseFirestore.podspec#L54 and the issue created on the CocoaPods repo CocoaPods/CocoaPods#10772.This appears to fix my issue and allows my applications to build and the LibXlsxWriterSwiftSample to build with 'BoringSSL-GRPC'.
The LibXlsxWriterSwiftSample uses the following pod file to run with
BoringSSL-GRPC
: