Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[!] CocoaPods could not find compatible versions for pod "ReactCommon/callinvoker"
See original GitHub issue[!] CocoaPods could not find compatible versions for pod “ReactCommon/callinvoker”:
In Podfile:
ReactCommon/callinvoker (from ../node_modules/react-native/ReactCommon)
None of your spec sources contain a spec satisfying the dependency: ReactCommon/callinvoker (from …/node_modules/react-native/ReactCommon).
You have either:
- out-of-date source repos which you can update with
pod repo updateor withpod install --repo-update. - mistyped the name or version.
- not added the source repo that hosts the Podspec to your Podfile.
From: Xcode 12.0.1 react-native@0.63.3 react@16.13.1
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:7
Top Results From Across the Web
CocoaPods could not find compatible versions for pod ...
For React native 0.62 version. So I figure it out. Replace following line in your Podfile pod 'ReactCommon/jscallinvoker', :path => ".
Read more >CocoaPods could not find compatible versions for pod ...
CocoaPods could not find compatible versions for pod "ReactCommon/jscallinvoker". Follow the below steps to resolve the issue.
Read more >React-native – CocoaPods could not find compatible versions ...
I just updated to RN v0.62 and running app on iOS gives me following error !] CocoaPods could not find compatible versions for...
Read more >cocoapods could not find compatible versions for pod "rct-folly"
Jul 23, 2021 ... It seems like you've changed the version of the dependency RCT-Folly somehow, it could happend when user try to...
Read more >CocoaPods could not find compatible ... - Code Grepper
replace pod 'ReactCommon/jscallinvoker', :path => "../node_modules/react-native/ReactCommon" //with pod 'ReactCommon/callinvoker', :path => ".
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 Free
Top 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
Seconding that comment above: I took
pod 'ReactCommon/callinvoker', :path => "../node_modules/react-native/ReactCommon"and replaced it withpod 'React-callinvoker', :path => "../node_modules/react-native/ReactCommon/callinvoker"It solved my problem!解决方法： pod ‘ReactCommon/callinvoker’, :path => “…/node_modules/react-native/ReactCommon” pod ‘ReactCommon/turbomodule/core’, :path => “…/node_modules/react-native/ReactCommon” 修改为 pod ‘React-callinvoker’, :path => “…/node_modules/react-native/ReactCommon/callinvoker” pod ‘ReactCommon/turbomodule/core’, :path => “…/node_modules/react-native/ReactCommon”