Undefined symbols for architecture arm64

[ankitbacancy]

🐛 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

same issue

[swrobel]

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

[dinukasal]

This works @swrobel, Thanks!

[swrobel]

Is anyone from the Flipper team digging into this at all...?

[mweststrate]

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: Is anyone from the Flipper team digging into this at all...? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN4NBFEOSNH3BCOLGVW7FLUBLRRFANCNFSM5ANEKJEQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[morphytron]

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: Is anyone from the Flipper team digging into this at all...? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2600 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN4NBFEOSNH3BCOLGVW7FLUBLRRFANCNFSM5ANEKJEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

When might this be supported per chance? Thinking about returning my M1 for an Intel-based laptop. Thanks!

[mweststrate]

Really hard to tell, its mostly downstream systems that make mobile dev hard on M1, some of our deps, Electron itself still dies, Android emulators... On Sat, 11 Sep 2021, 12:39 Apatiga, Daniel, ***@***.***> wrote:

…

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 … <#m_6196904304097146813_> On Sat, 11 Sep 2021, 06:22 Stefan Wrobel, *@*.***> wrote: Is anyone from the Flipper team digging into this at all...? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2600 (comment) <#2600 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN4NBFEOSNH3BCOLGVW7FLUBLRRFANCNFSM5ANEKJEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . When might this be supported per chance? Thinking about returning my M1 for an Intel-based laptop. Thanks! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN4NBFSLKA45TD7HCBIOM3UBM5VVANCNFSM5ANEKJEQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[swrobel]

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.

[fkgozali]

I was looking at the original commit that added this callsite (see facebook/folly#1655):

facebook/folly@0fee9df

It looks like that commit added c++abi linker flag to the build file, which I don't think we ever had in RCT-Folly.podspec and perhaps Flipper-Folly.podspec? Perhaps the fix is to somehow add that flag?

cc @mweststrate

[mweststrate]

@fkgozali / @swrobel interested in giving that a try? I'm still curious why it doesn't seem to be an issue with the reference project in that case (or is it?)

[yfeldblum]

Right, the function __cxa_increment_exception_refcount is exported, on Apple platforms, by dylib c++abi rather than by the more common dylib c++. While c++ depends on c++abi, the platform seems not to use transitive dependencies when resolving symbols. Since folly uses that function now, its cmake build sets up that direct link-time dependency. Since flipper is not using that cmake build, flipper would need to take the same steps.

[mweststrate]

Je n'ai aucune idée de ce que sont ces choses.

looping in @lblasa to read along.