-
Notifications
You must be signed in to change notification settings - Fork 107
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
BIT_CODE error while archiving #20
Comments
Hey @rajaishwary , are you setting bitcode enabled to The link to download bitcode enabled version of the framework is http://downloads.razorpay.com/Razorpay.framework-0.15.0-bitcode.zip |
Hi @akshaybhalotia .. Yes i have tried your suggestions but ended up disabling the BIT_CODE for the whole project. |
@rajaishwary what solution did you find for this as I also got the same error, and enabling BIT_CODE for this particular project does not work. |
which version of the package are you using and on which Xcode version are you doing so ? |
@iThink32 2.0.4 latest version on xcode 9.3 |
can u send a screenshot of the error that you are facing? |
I believe it is not a bitcode related issue , it is because you are trying to archive our framework as is , without removing the architectures added for running it on a simulator. please follow this tutorial and add the given run script to your build phases so that the simulator architectures are removed from all your existing frameworks.Im sure it will work after that this link explains why you are facing the error: and this link has the soln:- |
Thank you very much mate. That was the real issue. |
../ios/Razorpay.framework/Razorpay(RazorpayCheckoutViewController.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 armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
using RN 0.40.0 tried with enable bitcode too but the same error.
The text was updated successfully, but these errors were encountered: