-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
'folly/Portability.h' file not found #24192
Comments
Can you run If you believe this information is irrelevant to the reported issue, you may write `[skip envinfo]` alongside an explanation in your Environment: section.
|
same problem still goin for me. |
|
React Native Environment Info: |
same here: React Native Environment Info: |
Hello there 👋 this issue seems to be related to your experience upgrading between versions. We know this has been a long lasting pain for the community so starting v0.59 we have introduced a new flow via the new CLI. To upgrade to that version, you may still need to do some manual steps – we suggest you use rn-diff-repo to accomplish this. Given that this is not strictly a bug with the library itself I'll close this, but if someone can create a repro that has this issue with a freshly created |
Hi Lorenzo,
thanks for the information provided.
The project has been freshly set up with 0.59, I haven't done any version
upgrades since then.
Can you please be more specific about what made you think it is an upgrade
problem or what should we if it is not an upgrade problem but occurs on a
fresh new setup?
…On Mon, Apr 1, 2019 at 10:20 AM Lorenzo Sciandra ***@***.***> wrote:
Hello there 👋 this issue seems to be related to your experience
upgrading between versions. We know this has been a long lasting pain for
the community
<react-native-community/discussions-and-proposals#68>
so starting v0.59 we have introduced a new flow via the new CLI
<https://facebook.github.io/react-native/blog/#cli-improvements>.
To upgrade to that version, you may still need to do some manual steps –
we suggest you use rn-diff-repo <https://github.com/pvinis/rn-diff-purge>
to accomplish this.
Given that this is not strictly a bug with the library itself I'll close
this, but if someone can create a repro that has this issue with a freshly
created react-native init project we can reopen it and discuss it further
🤗
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#24192 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACOpgL1hKSE5gTag9b_mtL48wk4KfehFks5vchW8gaJpZM4cRuCt>
.
|
I changed react-native to previous version and this error went away. |
I resolved (on both 0.59.2 and 0.59.3) my removing from the Podfile: pod 'DoubleConversion', :podspec => "#{rn_path}/third-party-podspecs/DoubleConversion.podspec" Now I have only: rn_path = '../node_modules/react-native' pod 'yoga', path: "#{rn_path}/ReactCommon/yoga" and my other custom dependencies. |
@GabrieleTondi I don't have any of those. Added podspec for Folly, didn't help. Tried react-native 0.59.2, 0.59.3, no luck. |
I have a reliable Repro for this, it is not (only?) related to upgrading: https://github.com/bartolkaruza/issue-24192-repro Steps:
Podfile
Adding or removing this section in the Podfile had no effect
|
This is my current podfile
|
Adding the post_install is a confirmed workaround:
Leaving the issue open until we resolve the root cause (or update the doc to recommend this workaround 😄 ). Thanks @GabrieleTondi ! |
That's interesting. I've got this working without the post_install. |
I had this issue and it seemed to resolve when I added 'CxxBridge' to the React subspecs. I then removed my Podfile.lock and Pods folder and pod installed. I hope maybe this helps? |
@amphithere when I do it, it starts complaining about a missing "folly" pod. |
Sorry if this is a bit messy but this is my react native pod setup and it seems to be building successfully.
|
Thanks @amphithere, will try it if encounter this again. For now, just confirming that the solution by @GabrieleTondi worked for me as well. |
Encountered when I upgraded to 0.59.3
This worked! Thanks @GabrieleTondi |
I was able to eliminate the React post install script after adding the CXXBridge to the subspec. Good find @amphithere If others are looking for a solution to the duplicate UUID messages as a consequence of the post install script removing React, remove the post install script and CXXBridge to the subspec. [!] [Xcodeproj] Generated duplicate UUIDs: XCBuildConfiguration -- |
Hey guys, I got the same issue, but I'm not sure what's wrong, I'm using RN + RNFirebase. I've already tried the @GabrieleTondi solution and is not working using RN 0.59.3 or 0.59.6 the same result. this is my config:
When run
Also using the @amphithere solution is not working. PODFILE
I've already updated my Xcode, to 10.2.1 and now it's not working, my last RN was 0.57.7, so I need to fix this problem. The problem starts when I've installed Crashlytics on IOS because on Android is on production.
Please let me know if anyone knows what can I do? |
@cristianPerez I had an issue with iOS too when I upgraded to 0.59.3 and I essentially had to completely regenerate my iOS project by using the It's not very fun, but after doing that my project worked well with pods. I'm currently using React Native Firebase and it's running with Crashlytics. Here's my podfile just in case that helps.
|
Still waiting for an official solution. |
i have cleaned by :- still i am getting error in xcode 10 'folly/Portability.h' file not found, also cleaned the folder in xcode... can anyone help for this...? thanx |
same error here :( in iOS. |
Worked for me like this: In Xcode -> File -> Workspaces settings -> Build System changed to "Legacy Build System" (both, shared and per-user) and following what they have already put: rn_path = '../node_modules/react-native'
pod 'yoga', path: "#{rn_path}/ReactCommon/yoga"
pod 'React', path: rn_path, subspecs: [
'Core',
'CxxBridge',
'DevSupport',
'RCTActionSheet',
'RCTAnimation',
'RCTGeolocation',
'RCTImage',
'RCTLinkingIOS',
'RCTNetwork',
'RCTSettings',
'RCTText',
'RCTVibration',
'RCTWebSocket',
]
pod 'Folly', podspec: "#{rn_path}/third-party-podspecs/Folly.podspec"
# Project libs
# pod 'RNCAsyncStorage', path: '../node_modules/@react-native-community/async-storage'
post_install do |installer|
installer.pods_project.targets.each do |target|
if target.name == "React"
target.remove_from_project
end
end
end |
So far using the workaround. This fixed the podfile issue on react native 0.59.8 allowing me to consume @mapbox/react-native-mapbox-gl I am curious about the difference between
and
Should yoga be included for the workaround? Also after the workaround I am getting an error regarding duplicate UUIDs in the xcodeproject:
Is this anything to be worried about? |
In my case the problem occurred when I tried to link
and that was the start of the issue, wasted two days. I've deleted and then I can work again.. for the meantime, I decided not to use that library |
I found these answers only worked for me if I enabled the legacy build system. |
I tried all of the solutions mentioned here but still not working for me |
me too |
Awesome! This helped me, thanks a lot! |
Do confirm a fix without the post install script by adding CxxBridge to subspecs.
|
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. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
🐛 Bug Report
To Reproduce
Expected Behavior
Code Example
Environment
The text was updated successfully, but these errors were encountered: