Building existing iOS projects also start failing with the same error(s) if OpenSSL-Universal gets updated to 1.1.180 via pod update. Rolling back to OpenSSL-Universal 1.0.2.20 (Flipper-Folly 2.3.0 and Flipper-RSocket 1.1.0) seems to get the iOS build working again.

Building existing iOS projects also start failing with the same error(s) if OpenSSL-Universal gets updated to 1.1.180 via pod update. Rolling back to OpenSSL-Universal 1.0.2.20 (Flipper-Folly 2.3.0 and Flipper-RSocket 1.1.0) seems to get the iOS build working again.

In case anyone else is wondering how to do this, you need to add pod 'OpenSSL-Universal', '~>1.0.2.20' to your Podfile

In case anyone else is wondering how to do this, you need to add pod 'OpenSSL-Universal', '~>1.0.2.20' to your Podfile

One more note: you should also remove Podfile.lock before pod install
Just execute pod update

Ah my favorite. Random build breaks while updating core libraries. I applied @EricWiener 's code to Podfile and then issued a pod update and was successful. DIdn't need to blow away Podfile.lock as @Yadro was suggesting.
Mostly commenting to get my name on here and get an update when this issue is fixed so I can unpin OpenSSL-Universal.

@lauritaipale's solution worked for me, adding this to my pod file fixed the problem:

pod 'OpenSSL-Universal', '~>1.0.2.20'

NOTE: after adding this, just running pod install will fire an error due to versions mismatch, in that case remove Podfile.lock and pod install again

pod 'OpenSSL-Universal', '~>1.0.2.20'

NOTE: after adding this, just running pod install will fire an error due to versions mismatch, in that case remove Podfile.lock and pod install again

@aparedes this worked form me. I'm new to both react native and ios development. It's quite confusing to face such problems while running a helloWorldApp.

Updating cocoapods to 1.10.1 fixed the issue.

There seems to be an issue with xcframeworks on version 1.9.x (krzyzanowskim/OpenSSL#113 (comment))

Someone should fix this issue with npx, I get the same issue evertyme I create a simple app, please admin solve it.

Building existing iOS projects also start failing with the same error(s) if OpenSSL-Universal gets updated to 1.1.180 via pod update. Rolling back to OpenSSL-Universal 1.0.2.20 (Flipper-Folly 2.3.0 and Flipper-RSocket 1.1.0) seems to get the iOS build working again.

In case anyone else is wondering how to do this, you need to add pod 'OpenSSL-Universal', '~>1.0.2.20' to your Podfile

It worked for me. Thank you.

Try the following

cd ios
rm -rf Podfile.lock
pod install

I'm running into the same issue as @jonnyberanek . Has anyone figured out a fix?

by mistake i open .xcodeproj file instead of .xcworkspace.

I had this issue recently and the problem was with the outdated cocoapods (1.9) version. Updating to a newer version solved the issue.

sudo gem install cocoapods

This saved me
pod 'OpenSSL-Universal', '~>1.1.1100'

   use_flipper!({'Flipper-Folly' => '~> 2.6.9','Flipper' => '0.95.0'})
    post_install do |installer|
      flipper_post_install(installer)
    end

I am also using googleplaces and google maps so I had to add this
installer.pods_project.targets.each do |target| if target.name == 'react-native-google-places' target.build_configurations.each do |config| config.build_settings['CLANG_ENABLE_MODULES'] = 'No' end end if target.name == "React" target.remove_from_project end end

and
pod 'react-native-google-places', :path => '../node_modules/react-native-google-places'

Adding to help someone with similar issue. After switching to Big Sur and Xcode 12.5

Later I had this issue while generating a device build ___cxa_increment_exception_refcount"
so I had to make these changes
pod 'OpenSSL-Universal', '~>1.1.180'
use_flipper!({'Flipper' => '0.92.0', 'Flipper-Folly' => '2.6.7'})

For me the fix is just to change the Deployment Info target to iOS 11 or greater

For me, the issue was related to older Cocoapods version, updating my cocoapods fixed it
sudo gem install cocoapods

Updating cocoapods to 1.10.1 fixed the issue.

There seems to be an issue with xcframeworks on version 1.9.x (krzyzanowskim/OpenSSL#113 (comment))

This is the EXACT ANSWER

Updating cocoapods to 1.10.1 fixed the issue.
There seems to be an issue with xcframeworks on version 1.9.x (krzyzanowskim/OpenSSL#113 (comment))

This is the EXACT ANSWER

Will add that as requirement to the podspec itself