upgrade-support icon indicating copy to clipboard operation
upgrade-support copied to clipboard

Fixing issue with Open-SSL bitcode

Open EricWiener opened this issue 5 years ago • 1 comments

Environment

System:
    OS: macOS 10.15.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 986.72 MB / 32.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.16.0 - /usr/local/bin/node
    Yarn: 1.22.0 - /usr/local/bin/yarn
    npm: 6.13.7 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 26, 28, 29
      Build Tools: 28.0.3, 29.0.3
      System Images: android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.6010548
    Xcode: 11.4/11E146 - /usr/bin/xcodebuild
  Languages:
    Python: 3.7.3 - /Users/ericwiener/anaconda3/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Upgrading version

Upgrading from 0.61.5 to 0.62.0

Problem

Recieved the error:

'.../ios/Pods/OpenSSL-Universal/ios/lib/libcrypto.a(bio_lib.o)' does not contain bitcode. 
You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), 
obtain an updated library from the vendor, or disable bitcode for this target. for architecture arm64

Solution

For all your targets you need to go to Build Settings -> Enable Bitcode. Set Debug to NO and Release to Yes.

Screen Shot 2020-04-03 at 3 12 14 PM

EricWiener avatar Apr 03 '20 19:04 EricWiener

A more principled, long-term solution to this is open in the Flipper repository as https://github.com/facebook/flipper/pull/1171. In particular, I'm inclined to agree with this comment from the author:

it strikes me that not having access to current (and possible future) updates of a cryptography library is not a good long-term plan

chrisbobbe avatar Aug 27 '20 04:08 chrisbobbe