-
Notifications
You must be signed in to change notification settings - Fork 955
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion: Folly use of an OpenSSL pod that is built with bitcode turned on #485
Comments
Thanks @priteshrnandgaonkar! |
This shouldn't have been closed. The |
Please reopen, this is still an issue. I cannot debug on-device with react-native right now. |
Confirmed - this is starting to surface as support issues in other repositories - invertase/react-native-firebase#3384 - @priteshrnandgaonkar please reopen |
For affected react-native people - @matt-oakes - I turned bitcode off in debug builds and it worked, and I kept it on for release mode builds and sent it to TestFlight, it seems to work fine, so there's a workaround for now that seems to work okay |
Turning off Bitcode in debug builds triggered a lot of Swift Code errors. Please reopen and provide a fix. |
@priteshrnandgaonkar I apologize for my ignorance on how React Native / Flipper / Folly are all tied together but this was just merged yesterday and possibly solves this issue without having to disable bitcode? krzyzanowskim/OpenSSL#83 into The folly pod is locked to |
Per comment in facebook#485 (comment) it appears that OpenSSL will have bitcode information in it now which should solve problems like those experienced in facebook#485 and it's connected issues
I will check if updating the openssl dependency solves the bitcode issue. |
I tried using the latest openssl dependency with bitcode set enabled and disabled, but, I got the following error. Seems like the latest binary doesn't have all the symbols.
|
We depend on OpenSSL, unless we get the dependency of OpenSSL with bitcode enabled, Flipper, won't be able to support bitcode enabled in debug. As @mikehardy pointed out, you can disable the bitcode for debug builds and enable it for Prod builds as Flipper is not part of the prod builds. We would expect a fix regarding this from the community, as right now we are tied with this OpenSSL dependency which doesn't support bitcode. I am happy to try other dependency for OpenSSL, just let me know, if you find a good one. I tried using openssl-ios-bitcode. It builds the OpenSSL binaries(with bitcode support) when one builds the apps. Due to this the fresh build time were really slow. That's why we didn't use it. But maybe we can use the build script of it to build the openssl with bitcode support and then use that binaries directly just like krzyzanowskim/OpenSSL. |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
I can confirm that this issue still showing for |
Running into this after I updated Xcode to v12.
On |
@justinjoyn I think that is not related. This issue is about missing bitcode in a specific openssl release |
Am also facing this issue in react native 0.63.3 and Xcode 11.3 |
On Mojave, I am exploring upgrading Xcode to 11.7. If this works, I will update you. |
I can now confirm this works. It solved my problem. |
We're about to land an openSSL bump / bitcode fix, so should be solved by
next weeks version
…On Wed, Oct 14, 2020 at 7:59 AM Arun Jose ***@***.***> wrote:
I can now confirm this works. It solved my problem.
https://stackoverflow.com/a/61013836/2940495
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#485 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN4NBCS3AXHLXLCAJW3KALSKVD6PANCNFSM4H7ROMJA>
.
|
I am facing:
after upgrade to |
I updated Xcode from 11.3 to 11.7 |
Upgrading to Xcode 11.7 fixed it for me too (RN v0.63.3). |
Upgrading to Xcode 12 fixed it for me |
Upgrading to Xcode did nothing - what happened is they released a fix in their podspecs to similar to PR worked through here #1171 - it's resolved now via effort not magic ;-) |
@mikehardy I'm using Mohave 10.14.6 and XCode 11.0. Does this PR has to do with latest versions of XCode? Because with Flipper-Folly 2.3.0 I get the |
I don't know, given Apple requires you support their latest mobile operating system APIs, and the newer Xcode versions are required to do so, I can't imagine not using current stable Xcode, so I haven't tested 11 since 12 came out, and don't see the utility of doing so? |
Im having the same issue as of today. Using Catalina 10.15.7 on Xcode 11.3.1. with react-native: Update: Yes, updating to new Xcode 11.7 did actually solve my problem. Thank you! |
I also facing the same issue with you |
Only can solve the problem, who can update Xcode to 11.7? |
@mikehardy Does this fix work for macOS Mojave Xcode 11.3? or i have to update to macOS Catalina and install 11.7? |
I believe the general rule is that if you develop things for apple platforms you use the most up to date Xcode |
@mweststrate Hi, any news regarding the new version that should solve this issue? |
It's released, this is not a problem anymore. |
you can try these solutions https://stackoverflow.com/questions/29082174/ios-xcode-build-failing-due-to-openssl/76455587#76455587 |
Thoughts on switching to using a pod that includes bitcode support for OpenSSL which is a dependency of Folly such as openssl-ios-bitcode
Side note: anyone know which repo Follys podspec originates from?
The text was updated successfully, but these errors were encountered: