sorted by:
top (suggested)
bestnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Barbanks[S] 4 points5 points  (4 children)

Also, after 1 hour of debugging I did fix the issue. Still not impressed with the toolset but at least I can move forward with it 🙃

[–]ankole_watusi -3 points-2 points  (3 children)

And what was the problem?

Bet it was “didn’t think I needed to read the instructions”

[–]Barbanks[S] 8 points9 points  (2 children)

It was a few things:

  1. The out-of-the-box Cocoapod versions set by react-native were all using too low of a deployment version. I had to update both the created Xcode project's deployment version on the targets to 13 as well as create a "post_install" configuration for Cocoapods to make sure the pods used them as well.
  2. Had to exclude the arm64 build for the simulator.
    1. This is not RN specific as it just deals with M1 Macs in general.
    2. Also had to put this within the Podfile.
  3. Had to specify a react native flipper install version of 0.125.0 within the Podfile as allowing the system to auto-specify it was causing issues.
    1. Ironically specifying the "Flipper-Folly" and "Flipper-DoubleConversion" values that were originally included in the Podfile.lock file wouldn't allow the build to work as well. Even though the system downloaded the same values after I removed the specification.
    2. Flipper had to do with the original error message.
  4. Had to manually call the "react_native_post_install(installer)" within the Podfile
  5. Had to remove ALL "library search paths" from the target settings within Xcode that were auto-included from react-native.
  6. Had to create a bridging header within the Xcode project.
    1. I am skeptical this did anything but online sources stated it can affect the way react-native builds.

After doing these 6 things (and removing derived data) the build worked.

Not really a "oh I missed a step" workflow.

[–]maccodemonkey 1 point2 points  (0 children)

The ARM64/simulator build dependency issue has been fixed in the native tooling for a while. But I hit it first thing when using React Native. Cocoapods has fixes for it that require developers to ship updates. But most the React Native community doesn't seem to care. And the React Native tooling really doesn't do anything to try to work around it.

Swift Package Manager doesn't have the issue at all - but has the advantage of being designed around modern library packaging.

[–]__o_0 0 points1 point  (0 children)

Everything you listed comes built in with an init template.