-
Notifications
You must be signed in to change notification settings - Fork 42
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
Bitcode bundle could not be generated ... #29
Comments
Any update on this issue? I really need a solution soonish. I'd love to resolve it myself but my Objective C/Swift knowledge is very limited. Thank you in advance. |
You can simply disable Bitcode build https://stackoverflow.com/questions/30848208/new-warnings-in-ios-9 |
That worked fine. Thanks for that. |
I try to update the Linkedin SDK to its latest version (1.0.7 taken here https://content.linkedin.com/content/dam/developer/sdk/iOS/li-ios-sdk-1.0.7-release.zip) but it seems this project already has the latest version (I compare the md5 of each files). But I have still the same bitcode error :-( I look into the binary and it seems that the bitcode is here:
Does anybody have an idea on why it isn't building? |
@slestang were able to find a solution to this? I have the latest sdk but am still getting the same error. Also if I disable bitcode i get an error telling me to enable it. |
@slestang & @jacobbodkin You have to manually download LinkedIn SDK with bitcode support. https://developer.linkedin.com/docs/mobile-sdk-release-notes#ios |
@Misioka i thought i knew who to do this by replacing linkedin-sdk under RCTLinkedinLogin.xcodeproj but that did not work. Suggestions? |
The sample project builds and runs fine but it doesn't archive for pushing to App Store (TestFlight) I get the following error msg:
Bitcode bundle could not be generated because ... libRCTLinkedinLogin.a(Pods-dummy.o)' was built without full bitcode. All object files and libraries for bitcode must be generated from Xcode Archive or Install build for architecture armv7
Env vars
The text was updated successfully, but these errors were encountered: