Weird build failure on Xcode after updating to RN 0.66.1

[gabimoncha]

Description

After updating RN from 0.65.1 to 0.66.1, my iOS builds were failing with the following errors.

I thought one of the libraries I'm using is not compatible with the new version, so I've started a new project from the typescript template and added them one by one.
I turned out that that every time I add a new library with a native change, I get this error message and the only way to bypass it is by cleaning the project and restarting it with the following commands.

rm -rf node_modules ios/build ios/Pods ios/Podfile.lock && yarn cache clean
yarn && cd ios && pod install && cd ../
yarn start --reset-cache

React Native version:

System:
 OS: macOS 11.6
 CPU: (8) arm64 Apple M1
 Memory: 353.69 MB / 16.00 GB
 Shell: 5.8 - /bin/zsh
 Binaries:
 Node: 16.9.1 - /opt/homebrew/bin/node
 Yarn: 1.22.11 - /opt/homebrew/bin/yarn
 npm: 7.21.1 - /opt/homebrew/bin/npm
 Watchman: 2021.09.13.00 - /opt/homebrew/bin/watchman
 Managers:
 CocoaPods: 1.11.2 - /opt/homebrew/bin/pod
 SDKs:
 iOS SDK:
 Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
 Android SDK:
 API Levels: 29, 30, 31
 Build Tools: 29.0.2, 30.0.2, 31.0.0
 System Images: android-31 | ARM 64 v8a, android-31 | Google APIs ARM 64 v8a, android-31 | Google Play ARM 64 v8a
 Android NDK: Not Found
 IDEs:
 Android Studio: Not Found
 Xcode: 13.0/13A233 - /usr/bin/xcodebuild
 Languages:
 Java: 1.8.0_292 - /usr/bin/javac
 npmPackages:
 @react-native-community/cli: Not Found
 react: 17.0.2 => 17.0.2 
 react-native: 0.66.1 => 0.66.1 
 react-native-macos: Not Found
 npmGlobalPackages:
 *react-native*: Not Found

Steps To Reproduce

1. Init a new project (I tested only on Typescript)
2. Install dependencies, build from Xcode
3. Install a library any native change so that you can pod install after too (I guarantee it works with the following: react-native-svg + react-native-svg-transformer, react-native-reanimated, react-native-device-info, react-native-dotenv, react-native-file-logger, react-native-safe-area-context)
4. Restart metro and rebuild from Xcode

Expected Results

App should build successfully as it normally does.

[gabimoncha]

@lunaleaps I don't think this issue should be closed and I'm not sure if this is an upgrade issue.

[lunaleaps]

Ooops, I didn't know we had that github action -- I had not intended to close it but properly label this to help signal how many issues people have upgrading to a release. Let me fix

[Ppang0405]

Thanks @gabrielmoncea , your workaround worked for me. But this bug is still annoying.

[carbopilot]

It's also a problem with a new react-native project .., not just an upgrade.

[carl0shd]

This is happening to me since React Native 0.66.0, the bug starts from this version.

[lunaleaps]

For the steps to repro, can you share the commands you're running? And maybe a specific native package?

[chengsam]

I just come across this error and cleaning build folder in Xcode worked for me, but I'm not sure if this works all the time

[Deepacks]

I am currently facing two different issues:

• RCTFolly:
  I managed to solve this one with this fix Typedef redefinition with different types ('uint8_t' (aka 'unsigned char') vs 'enum clockid_t') when building latest react-native rc with macOS target facebook/flipper#834 (comment)

• RCTVibration:
  I have not yet found a fix for this, not even the steps suggested in this issue.

Using the latest cocoapods version to install the pods (Mac M1 silicon)

The following is the current build error, hope it can be somewhat useful

[carl0shd]

I just come across this error and cleaning build folder in Xcode worked for me, but I'm not sure if this works all the time

Yep, this works for me too, but the behaviour is the same, this error only appears if I update or install a native library, if I don't do any of that Xcode does not generate an error.