Xcode 12.5 troubleshooting guide (RN 0.61/0.62/0.63/0.64)

[kelset]

Hey folks.

This issue wants to be a follow up to #31179; that issue has become really long so opening a new one to try and reduce the noise and confusion around it.

Here is how to fix the Xcode 12.5 iOS build breaks with errors related to "atomic_wait_until is unavailable" (and similar messages).

(sidenote: make sure you are using cocoapods 1.10.x)

If you are on 0.61

Note well: this has only been tested by a few members of the community, not by me, so I can't ensure it will work.

If you are still using RN 0.61, you can refer to this comment #28405 (comment) from @edgarbonillag.

If you are on 0.62

1. add this line to your podfile (or modify it if you already had it):

use_flipper!({'Flipper' => '0.75.1', 'Flipper-Folly' => '2.5.3', 'Flipper-RSocket' => '1.3.1'})

2. change your package.json react-native dependency to

"react-native": "0.62.3"

3. do all the classic necessary cleans (node_modules, caches, pod folders, etc)(react-native-clean-project is your ally) then do yarn install and a pod install --repo-update (if pod install fails on an error about a Flipper package, just remove the relevant lines from the podfile.lock and run the pod install again)

If you are on 0.63

Note well: you need to be on latest 0.63.x release, at the time of writing 0.63.3.

If you are on 0.63, you are in luck! You just need to add this line to your podfile (or modify it if you already had it):

use_flipper!({'Flipper' => '0.75.1', 'Flipper-Folly' => '2.5.3', 'Flipper-RSocket' => '1.3.1'})

Then properly clean your caches (react-native-clean-project is your ally), remove pods folder and do a pod install --repo-update.

This should be enough for you to get Xcode 12.5 to work.

If you are on 0.64

1. (optional) check your podfile.lock and make sure that Flipper is on 0.75 or higher, and Flipper-Folly is 2.5.3 or higher; if not, add this line to your podfile (or modify it if you already had it):

use_flipper!({'Flipper' => '0.75.1', 'Flipper-Folly' => '2.5.3', 'Flipper-RSocket' => '1.3.1'})

2. change your package.json react-native dependency to:

"react-native": "0.64.1" // or higher

3. do all the classic necessary cleans (node_modules, caches, pod folders, etc)(react-native-clean-project is your ally) then do yarn install and a pod install --repo-update (if pod install fails on an error about a Flipper package, just remove the relevant lines from the podfile.lock and run the pod install again)

---

These scenario have all been tested and ✅ so if you are still experiencing issues, it's likely that it's caused by some local configuration getting in the way. If that's the case, please refer to this comment by @smadan.

---

If none of the above helped you, and you can reproduce your issue consistently - even on a freshly init'd project, then post a comment below with how to repro so that this can be investigated further.

[Dag0n]

Debugger/DevTools is still not loading with these fixes in place.

info Opening flipper://null/Hermesdebuggerrn?device=React%20Native...
info Opening flipper://null/React?device=React%20Native...

appears in the terminal window but no windows open.
Device M1 Macbook Pro

    "react": "17.0.1",
    "react-native": "0.64.1",

  - Flipper (~> 0.75.1)
  - Flipper-Folly (~> 2.5.3)
  - Flipper-RSocket (1.3.1):

E: If anyone has any workaround that'd be good as idb facebook/idb#649 hasn't been updated to run on M1 and hermes is not supported on iOS simulator.

[rbackhouse]

My experience with following the instructions for a 0.62.2 project did not match what I actually had to do

1. My Podfile did not have a "use_flipper!" call but instead a "add_flipper_pods!" call.
2. The add_flipper_pods def is embedded in the Podfile.

For it to work I had to

1. Add require_relative '../node_modules/react-native/scripts/autolink-ios'

2. Remove the whole "def add_flipper_pods!(versions = {})" block and "def flipper_post_install(installer)" block

3. Change add_flipper_pods! to add_flipper_pods!('Flipper' => '0.75.1', 'Flipper-Folly' => '2.5.3', 'Flipper-RSocket' => '1.3.1')

With these change project now builds again.

[mikehardy]

Just a note for people running react-native builds on BitRise - it appears that BitRise restores caches as read-only by default and you need to delete the build cache after updating to 0.64.1 before the build will work, but then it will work repeatedly

That guess is based on this evidence

• the build failed there during the pod post install hook, where the method signatures are patched to fix the build. The specific failure was an rb.sys_open failure with permission denied
• knowing what the patch release was trying to do (edit files in the Pods directory in the post install hook), and guessing about the read-only restore hypothesis, the cache was deleted
• rebuild then worked, and subsequent builds worked.

Hope this helps !