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
Undefined symbols for architecture arm64 #2600
Comments
same issue |
This works @swrobel, Thanks! |
Is anyone from the Flipper team digging into this at all...? |
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! |
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>.
|
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 was looking at the original commit that added this callsite (see facebook/folly#1655): It looks like that commit added cc @mweststrate |
Right, the function |
Je n'ai aucune idée de ce que sont ces choses. looping in @lblasa to read along. |
@yfeldblum thanks for your comment. I'll try to look into this very shortly. As @mweststrate pointed out, I do not understand why this is not an issue with the reference project? |
@lblasa seems we don't run against ARM64 in CI. Not sure anymore if that is intentional ('we don't support it') or due to CI limitations? https://github.com/facebook/flipper/blob/main/.github/workflows/iOS-Sample.yml#L30. But for usage on Intel Macs in generally we don't need to build for ARM64 anyway correct? @swrobel are ARM64 builds deliberately targeted in your build process? (asking as someone who is an iOS noob, so this might be a stupid question) |
Wish I had the answer here but I guess React Native abstractions have rendered me ignorant. I just assumed since iOS devices are arm64 that the app has to be built for that platform for App Store submission. |
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: facebook/react-native#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 |
Same issue here: iOS: 14.7.1 |
I don't see any reproducible example here, so all I can say is "it works for me", so who's right? Is it working or is it not? An example would cut through all confusion: https://stackoverflow.com/help/minimal-reproducible-example |
Ah wait just saw this: fixed and already picked for 0.66, and likely after 0.65.1 so my testing sees it as already fixed: facebook/react-native@b0c8a4e |
For M1 devices, I've just commented this line in the Podfile if you want to build your binary on a physical device:
You can uncomment it for release build |
@felix-lambert, looks like you are pointing to outdated versions, I recommend to either use |
I see it in our Sample iOS app as well. Downgrading to Flipper-Folly 2.6.7 helped. |
Closed by db59652 |
Can we also update the example podfile? https://github.com/facebook/flipper/blob/main/react-native/ReactNativeFlipperExample/ios/Podfile |
@xilin thanks for raising this, I will make the update. |
Summary: This change bumps Flipper-Folly to the latest which fixes an issue with undefined symbols. See #2600 Reviewed By: aigoncharov Differential Revision: D32528018 fbshipit-source-id: 24458e43eedd4afad5049b72991bc5e013e67171
In my case the problem was different. I found that when launched In the screen I put the right version. To fix, call
Launch again |
🐛 Bug Report
Throws an error of arm 64 when running app from Xcode 12.4 to iOS 14.6
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
The text was updated successfully, but these errors were encountered: