flipper: Undefined symbols for architecture arm64
🐛 Bug Report
Throws an error of arm 64 when running app from Xcode 12.4 to iOS 14.6
Undefined symbols for architecture arm64:
"___cxa_increment_exception_refcount", referenced from:
folly::cxxabi_cxa_exception_sans_reserve() in libFlipper-Folly.a(Exception.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
To Reproduce
Run app on device iPhone 12 contains iOS 14.6
Environment
Flipper Desktop version: .98.0 iOS: 14.6 XCode version: 12.4 react: 16.11.0 react-native: 0.62.2 device: iPhone 12 flipperkit version in Pods: 0.96.1
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 27
- Comments: 26 (11 by maintainers)
Closed by https://github.com/facebook/flipper/commit/db59652d0ef2244228db4634c0b2cf9cf55239d4 Please, upgrade to Flipper-Folly 2.6.10.
Je n’ai aucune idée de ce que sont ces choses.
looping in @lblasa to read along.
This is actually happening for me on an Intel Mac. I’m working on trying to get my project to build by trying various things people have said worked in github issues … then I’ll try the reference project.
I’ve been working to get react-native core and template to work on M1 macs and just for reference - related to a question above - I can say debug and release builds done on an M1 for simulator fail in different ways than release builds done on an intel mac (which do target arm64 as a cross-compile), despite their both being for arm64. Unexpected but widely reproduced experimental results there. Reference: https://github.com/facebook/react-native/issues/31941
Also, I’m unaware of M1 abilities from CI providers at the moment in general, certainly not GitHub, unfortunately, so having this tested automatically is not possible anywhere at the moment, it’s all done currently via folks like myself or reporters here running tests and reporting during react-native release process.
Happy to see any effort here or elsewhere ironing things out there, much appreciated
I can confirm that downgrading Flipper-Folly from 2.6.9 to 2.6.7, as recommended here and here, fixes the issue for me.
iOS: 14.7.1 XCode: 12.5.1 macOS: 11.5.1 (intel) flipperkit: 0.102.0
same issue
@felix-lambert, looks like you are pointing to outdated versions, I recommend to either use
use_flipper!()for the defaults of the React Native version you are using (should work on M1 icmw RN 0.66), or otherwise try the versions in our reference project: https://github.com/facebook/flipper/blob/main/react-native/ReactNativeFlipperExample/ios/Podfile#L30For M1 devices, I’ve just commented this line in the Podfile if you want to build your binary on a physical device:
# use_flipper!({ 'Flipper' => '0.96.0', 'Flipper-Folly' => '2.6.7', 'Flipper-RSocket' => '~> 1.4' })You can uncomment it for release build
Could you compare your setup against the reference project in this repo in the react native folder? Please note that we don’t support building for M1’s yet
On Sat, 11 Sep 2021, 06:22 Stefan Wrobel, @.***> wrote: