Error upgrading 0.64 -> 0.66 CocoaPods could not find compatible versions for pod "RCT-Folly"
See original GitHub issueDescription
trying to upgrade to latest version to have access to RippleConfig.foreground
in 0.66 but running into this issue on the ios side
React Native version:
System:
OS: macOS 10.15.7
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 255.71 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.17.3 - /usr/local/opt/node@14/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.13 - /usr/local/opt/node@14/bin/npm
Watchman: 2021.06.07.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 28, 29, 30
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.0, 30.0.2
System Images: android-29 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.6858069
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_242-release - /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
Provide a detailed list of steps that reproduce the issue.
- have 0.64 ejected project
- try to update to latest 0.66
- run
npx react-native upgrade
Expected Results
successful upgrade
Snack, code example, screenshot, or link to a repository:
Auto-linking React Native modules for target `mobile`: RNCAsyncStorage, RNCMaskedView, RNGestureHandler, RNKeychain, RNScreens, RNVectorIcons, react-native-image-picker, and react-native-safe-area-context
Analyzing dependencies
Fetching podspec for `boost` from `../node_modules/react-native/third-party-podspecs/boost.podspec`
[!] CocoaPods could not find compatible versions for pod "RCT-Folly":
In snapshot (Podfile.lock):
RCT-Folly (from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`)
In Podfile:
FBReactNativeSpec (from `../node_modules/react-native/React/FBReactNativeSpec`) was resolved to 0.66.1, which depends on
RCT-Folly (= 2021.06.28.00-v2)
RCT-Folly (from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`)
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
at makeError (/Users/x/go/y/mobile/node_modules/execa/index.js:174:9)
at /Users/x/go/y/mobile/node_modules/execa/index.js:278:16
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async installDeps (/Users/x/go/y/mobile/node_modules/@react-native-community/cli/build/commands/upgrade/upgrade.js:208:3)
at async Object.upgrade [as func] (/Users/x/go/y/mobile/node_modules/@react-native-community/cli/build/commands/upgrade/upgrade.js:346:9)
at async Command.handleAction (/Users/x/go/y/mobile/node_modules/@react-native-community/cli/build/index.js:186:9)
info Run CLI with --verbose flag for more details.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
RCT-Folly error when using hermes with iOS - Stack Overflow
It seems like you've changed the version of the dependency RCT-Folly somehow, it could happend when user try to copy podfile or dependencies ......
Read more >cocoapods could not find compatible versions for pod "rct-folly"
Error : Compatible versions of some pods could not be resolved. You are seeing this error because either: - Versions in the Podfile.lock...
Read more >CocoaPods could not find compatible versions for pod ... - Ionic
but they required a higher minimum deployment target. To resolve this error, set the minimum iOS version to 13.0 within your Podfile :...
Read more >Troubleshooting - React Native
If you see the following error after running pod install : [!] CocoaPods could not find compatible versions for pod "RCT-Folly":.
Read more >Cocoapods Could Not Find Compatible Versions For Pod
Error upgrading 0.64 0.66 CocoaPods could not find compatible versions for pod RCTFolly #32423.Closed.1mike12 opened this issue on Oct.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Try running
pod update && pod install
in ios folder to fix this issue.I ran into a similar issue before. Renaming or deleting the
Podfile.lock
and re-runpod install
worked for my case.