-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
iOS Pod issues #17893
Comments
Same issue |
The PR does fix the issue #17764 |
Same issue
Add any other subspecs you want to use in your project] RN >= 0.42.0pod "yoga", :path => "../zm_parents/node_modules/react-native/ReactCommon/yoga" |
How to solve this problem |
Archiving an iOS build seems broken with the new Cocoapods 1.4.0 as well. Downgrading it to 1.3.1 seems to help. |
Also getting this |
@makovkastar That's what I did at first, and indeed it works, but it would be cool to be able to use the latest version :) |
@Plo4ox downgrading seems the most reliable option: I tried 0.52, 0.53 and even 0.54-rc with no more success... |
Same issue here. Don't think, that downgrading is something, that is supposed to be the best solution :) UPDATE |
@FlyOrDie I also had to remove the inherited header search paths to get it to build, haven't had time to investigate further. |
@msand A strange thing helped me to solve the problem. I don't even know, why I did it. In pods file, I changed the sequence... from: to: Started working. It is not related to cache in any way, because I was dropping caches of everything, including NPM every time to make experiments clean 🗡 |
+1 encountering this issue as well, if one has to downgrade so be it, but this should not be the solution. |
it's still exists ! |
I am also encountering this issue when trying to upgrade from 0.51.0 to 0.52+ |
I hadn't noticed this was using the "use_frameworks!" my issues we're probably unrelated. Managed to get use_frameworks building with the patches from here: #17764 (comment) but archiving fails on 0.54 with this: #18205 |
@msand I wrote a comment on this issue #18205 |
I think at this point it's probably good to made a single PR with all the needed patches to have it working with manual linking, normal cocoapods, and cocoapods with use_frameworks! on. |
Found another workaround for the non use_frameworks case: #15838 (comment) Essentially a duplicate target for debugging with manually linked React Native modules, and using the xcodebuild cli to build release for simulator and archive for TestFlight / AppStore. |
Having this issue on version 0.55. Did anybody find a solution? |
@The0racle After a quick glance at the version 0.55.2, I had the following issue: |
Change use_frameworks! ==> # use_frameworks! ? |
To apply patches automatically you can use the |
Thanks for posting this! It looks like your issue may refer to an older version of React Native. Can you reproduce the issue on the latest release, v0.55? Thank you for your contributions. |
@Plo4ox Any progress on this ?? Thanks in advance |
@NrqhEIcsRi004 good! version 0.55.4 works~ |
@xiaoxiaocainiao I am experiencing this problem in a new project using version |
react-native @0.55.4 have the same issue
|
I am using react-native@0.53.3. I faced all these issues. As suggested by others, I tried below steps,
Anyone else faced similar issue? Any suggestions on fixing it? |
I copied snipped from below location in my podfile and it seems to work fine, It would have been awesome if react team could have fixed all these in a patch to 0.53 version and corresponding dependencies. |
Please verify using the |
Getting this no matter what I do. I've updated the header search paths to search the React folder (recursive as well) in the node module folder and I've linked all libs.
However Xcode does not show a React folder in the Pods project's Pods folder, despite it being there in Finder (but this seems to be normal according to other guides I've found). And these undefined symbols' headers I can locate in Pods/Headers/React/React, which is strangely 2 React folders deep, is that correct? I've tried so many different things and it cannot find these symbols. Also get these warnings which probably has something to do with it:
Which I've also tried to fix by changing the Pods project to Build Active Architectures = No No luck. |
@willswinson can you confirm this is happening in 0.56? |
create a empty swift file and bridgeing-header file can fix this |
Are you guys removing all *.xcodeproj from the Libraries section to prevent libraries from being compiled and linked twice? |
@ricsam yes, but you need to add a new start package script in your project build phrase |
@willswinson @hramos Experiencing the same issue with 0.56, or something similar at least.
|
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 "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions. |
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: macOS High Sierra 10.13.3
Node: 9.4.0
Yarn: Not Found
npm: 4.6.1
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 3.0 AI-171.4443003
Packages: (wanted => installed)
react: 16.2.0 => 16.2.0
react-native: 0.53.0 => 0.53.0
Target Platform: iOS (11.2)
Steps to Reproduce
Follow the tutorial presented here:
https://facebook.github.io/react-native/docs/integration-with-existing-apps.html
Expected Behavior
Succeed to build the app.
Actual Behavior
it doesn't work .
I'm kidding, the build just failed with the following errors:
Those errors occur while building module 'yoga' imported from
React/Base/RCTConvert.h
Reproducible Demo
You can get the non working project on the following repo:
% git clone https://github.com/Plo4ox/ReactNativeIssues.git
% cd ReactNativeIssues
% npm install
% cd ios
% pod install
% cd ..
% react-native run-ios
Or just follow the steps:
% create-react-native-app AwesomeProject
% cd AwesomeProject
% mkdir ios
// Modify the package.json file fill it content indicated in the documentation:
% npm install --save react@16.2.0 react-native
// Create a new single view app project into the iOS directory, using Xcode
% cd ios
% pod init
// Fill the Podfile with the content indicated in the documentation, be sure to keep your default target
% pod install
% cd ..
% react-native run-ios
Pull Request
A PR related to this issue has already been created here:
#17764
The text was updated successfully, but these errors were encountered: