Unable to run fresh new React Native project (possible arm64 processor issue) #31118
Comments
|
You should comb through other issues that people are logging related to M1 Is your issue the same as #30836 that you linked above? That is still active. |
|
For anyone having M1 chip issues like this: Turning on
You'll need rosetta installed Open application > utilities > Terminal. Right click > Get Info > Toggle Open using rosetta I was able to run without it before, I'm wondering if it's something to do with Flipper not supporting For anyone struggling to understand the differences between |
|
I tried Here there's a nice setup for M1, even though it did not work for me either. |
|
For my case, I had to exclude post_install do |installer| And specify the flipper version Then, I cleaned my pods and reinstalled it : And now I'm able to build 💯 See https://stackoverflow.com/a/65399525 to understand why we need to exclude |
|
I followed @alimtunc advice plus: And I did the same for the Pods such a Flipper and YogaKit because the past year I face a similar issue with the arch and I fixed it excluding arm64 from this two Pods. Version OS: 11.4 (20F71) Xcode: Version 12.5.1 (12E507) The terminal and XCode are not running with Rosetta. After all of this I was having troubles with Ruby, but there's thread already opened here that solves that problem. |
|
@alimtunc Thank you! Solved my issues for building for two projects. Hocam eline sağlık tekrar :) |
|
I combined @alimtunc and @DracotMolver solutions plus excluding it also in xcodeproj fixes the problem. The thing that worries me is that after applying it, if I cold start the app on iOS simulator (kill and reopen) I get the Warning. |
|
I have re-runned |
|
Excluding |
|
If anyone is still struggling with this on M1's, just install Rosetta (softwareupdate –install-rosetta) and then go to Finder > Right click on Xcode > Get info > Enable "Start with Rosetta". This will make Xcode and respective builds to run correctly and will make it possible to generate Archives and so on, the only opposite side is that it runs slower than normally running. |
- Add dependency on vision-camera-code-scanner
- Only activate camera when screen is focused
- FrameProcessor runs once per second since the docs state:
> A value of `1` indicates that the frame processor gets executed once per second, perfect for code scanning.
- But consider increasing to 5 in the future since the docs also state:
> For a QR Code Scanner, 5 FPS (200ms) might suffice
- Known issues: Lines 23-25 of QRCamera.tsx sometimes cause the following error when
navigating back from JoinOrg:
```
ERROR Warning: Can't perform a React state update on an unmounted component. This is a
no-op, but it indicates a memory leak in your application. To fix, cancel all
subscriptions and asynchronous tasks in a useEffect cleanup function.
in QRCamera (at CameraControl.tsx:19)
```
Thanks! It worked. |
|
Please people STOP recommending Rosetta so that we can actually find a REAL FIX for this solution 🤦 |
|
any updates on this? |
|
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
This issue was closed because it has been stalled for 7 days with no activity. |
Description
Unable to run react-native on brand new (and existing) projects. Possible ARM processor issue, running out latest MacBook Pro with M1 chip. I first experienced it on a going project then I created a fresh new project to test it.
React Native version:
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
npx react-native init AwesomeProjectyarn iosExpected Results
Expected App to start
Errors
Followed suggested fixes mentioned on #30836
In
Podfile, tried both:and
PodsandPodfile.lockfiles.pod installyarn iosGet the following errors:
Anyone else experiencing the same?
The text was updated successfully, but these errors were encountered: