-
Notifications
You must be signed in to change notification settings - Fork 954
Flipper doesn't build with Xcode 12.5 RC #2215
Comments
I'm getting the same error in our React Native app. Here's some related issues I was able to dig up: Looks like the underlying issue was resolved (here: facebook/folly@8477e25), but it hasn't been published to cocoapods yet. |
Same as you. I feel no hope right now. |
xCode 12.5 has released yesterday, this error still here. I hope we will be resolve the error for the next version |
Same issue by updating Xcode and my devices. Try many solutions but no one work. |
I read facebook/folly@8477e25, the issue has resolved but flipper does not update yet |
same issue but why even I still disabled flipper on ios and I'm still getting a build error? |
Now, i just need update this file and it run normally. Hope it will be resolve in the next version. facebook/folly@8477e25#diff-65ad309ca9c636ba81eb7953fce06e6963c51296a60dc25eb4a5b1463482c6da |
Me too - I get the following:
|
Anyways, I was able to fix this by downgrading to XCode Version 12.4. It seems the issue for me happens when I updated my Xcode to the latest 12.5 version. until there's a patch to fix this, i will continue using 12.4 version |
This disables Flipper, but it's a quick workaround if you (like me) need the project working again.
|
However this ain't working, tried numerous times there's still a build error. :( |
Summary: `std::atomic_wait()` and `std::atomic_notify_one()` are marked as unavailable. Not really sure what that means, but it seems to be breaking some open source builds #1527. Explicitly qualify the calls into those functions to try and fix the build break. Since we cannot conditionally import either of the above (because they are marked as unavailable), we can't rely on the standard implementations. To prevent ADL from kicking in when the standard-library defines these, we fully qualify these and use `tag_invoke` for the customization points used in tests. Reviewed By: davidtgoldblatt Differential Revision: D26742072 fbshipit-source-id: 9f44bbfd37530f5ecffa3e03d673cfb1df953299
Managed to use the temporary code fix above posted by j2teamlbh, what made it finally work was ensuring that in the podfile you specify that you're using |
Sucks. |
@AlexHooperDev you wouldn't happen to know where I would put that change in my Podfile would you? I'm using using react native 62
|
It's up to you but I would put it below |
I will take a look at this by today or tomorrow and will release a new Flipper-Folly version. |
The newer version of Folly depends on new dependency called fmt. So we will have to add a cocoapod dependency for that as well. Right now I am stuck at an issue from fmt where the xcode is not able to find the definition of the compile function. The changes related to flipper-folly pod and fmt pod can be found here. When I run
Any idea how can I solve this ? |
I have solved the above error. Now fixing the other errors. |
I have released a new Flipper-Folly version of 2.5.2. Give it a try. It points to the latest Folly release. The latest folly release also depends on a fmt library, the pod of which is also published as Flipper-Fmt. Do try using Flipper-Folly version of 2.5.2 and let me know if it fixes the issue. |
How are we to update Flipper-Folly? |
Run |
tried but still same error |
@priteshrnandgaonkar deleted the podfile-lock and folder, those commands still led me to install 2.5.1 |
I seem to get 2.5.1 no matter what, and I don't have a hash in the lockfile locking it to that version |
@avery-pierce Yea @nicholasc 's advise on downgrading back to 2.5.1 and following #2215 (comment) did not work for me. I'm trying to get my app on testflight. (product->analyze) hopefully this is the case for some of you |
For now I've disabled Flipper on iOS and our project builds now |
What specifically you did for it? |
As a hotfix I have patched 2.5.1 with the above mentioned patch in Flipper-Folly 2.5.3 I will follow up with RN folks regarding consolidating Flipper-Folly and RCT-Folly into one and have a consistent workflow of maintaining it. But for now Flipper-Folly 2.5.3 should unblock. |
This worked for me, thanks! |
In Podfile comment the following:
Then |
It would be nice if you could get with them and get them to commit to removing Flipper from CRNA and expo init. This package is below 1.0, is woefully slow and plagued by instability and performance variance between different versions and frequently has breaking changes. It doesn't belong in starter templates and it shouldn't be a requirement for getting started with React Native. The amount of downtime, CI slowness, failed and slowed builds it has caused could probably be valued in the hundreds of thousands of $$$, all because someone made the decision to make the RN community guinea pigs for this tool. Reactotron is infinitely better despite being created by a third party, not updated for 2 years and swizzling APIs that Facebook didn't open to it. I have a 2020 MBP and Flipper performs terribly on it. What audience is this tool really intended for if it can't perform on a new MBP, breaks frequently, and slows down people's builds? Now lets say it finally performs like its contemporaries, tools like VSCode or whatever else. Then I'd understand, and I'd probably even use it. But why is it in production now in the state that it is? |
This worked for me. On react native 0.63.4 |
THANKS |
Trying the above got me past the errors others described, but I'm now running into from the Podfile.lock:
A somewhat recent issue on the subject is here I'm newish to react-native when it comes to custom managing the versions like this, does anyone have any advice on how I can resolve? |
@priteshrnandgaonkar will check it out later. thank you for staying on top of this. |
After updating to Flipper-Folly 2.5.3 I'm getting this build error: |
@kkelley-leftbrain I got past OpenSSL issues by adding the version of OpenSSL-Universal in the Podfile:
In my case it was previously pinned to an older version. |
Still getting the same error after updating and reinstalling pods ?
|
Yes because they have updated Flipper-folly not RCT-folly,
|
This works perfectly! Just do |
@umang-simform the solution you gave is giving me open ssl error while installing/updating pods. [!] Error installing OpenSSL-Universal
[!] /usr/bin/git clone https://github.com/krzyzanowskim/OpenSSL.git /var/folders/p8/8d4bmlwn6858cz1x0szgzv940000gn/T/d20210429-20276-18dmikn --template= --single-branch --depth 1 --branch 1.1.180
Cloning into '/var/folders/p8/8d4bmlwn6858cz1x0szgzv940000gn/T/d20210429-20276-18dmikn'...
error: 7467 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: index-pack failed |
After doing this, I am getting the following error:
Any ideas ? |
Those getting RCT-Folly errors, please follow facebook/react-native#31179 I am closing this as the issue from Flipper side is resolved. |
Thanks @umang-simform this worked great for our team, we just had to add the following line before calling
|
Hey guys they push a new version. You just need to edit your code to that
And |
@AlixH did you find a solution to this? been getting the same error. |
@my-name-is-nheo @AlixH I'm having a very similar error. I ended up giving up and just downgraded back to xcode 12.4 😞 |
Guys please stop asking, read the comments, they already fixed it and they give the solution |
|
sorry, but where we can find this final solution? Would be great if someone can pin it for us please. I updated to Big Sur, so I have now XCode Version 12.5 (12E262), I also updated from 0.63.4 to 0.64.0 but XCode build still fails. Would be great if we can build our app again and ship them to the clients in the very next few days. Thanks |
|
Locking now since the original issue is solved. Please see the comment directly above and this one. For RTC-Folly issues please follow up in facebook/react-native#31179. For any new issues open a fresh issue including Podfile & lock file |
🐛 Bug Report
Flipper in a React Native project fails to build with the following error:
Build log
Cleaning the Xcode build folder didn't help, nor does updating Flipper and Flipper-Folly to the latest versions.
To Reproduce
Environment
The text was updated successfully, but these errors were encountered: