CocoaPods could not find compatible versions for pod "Flipper-Folly"
Asked Answered
K

13

31

I have been trying to run ios for a new but kept getting this error

** BUILD FAILED **


The following build commands failed:
        CompileC /Users/struggle/Library/Developer/Xcode/DerivedData/client-grabnjjdhfcfyugfdqcwdvbebnva/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/Flipper.build/Objects-normal/x86_64/FlipperRSocketResponder.o /Users/struggle/Desktop/Tax/client/ios/Pods/Flipper/xplat/Flipper/FlipperRSocketResponder.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

I saw a solution that said to add use_flipper!({ 'Flipper-Folly' => '2.3.0' }) in my podfile now when i run pod install i get the following error

`[!] CocoaPods could not find compatible versions for pod "Flipper-Folly":

In Podfile:
Flipper-Folly (= 2.3.0)

FlipperKit (~> 0.54.0) was resolved to 0.54.0, which depends on
  FlipperKit/Core (= 0.54.0) was resolved to 0.54.0, which depends on
    Flipper (~> 0.54.0) was resolved to 0.54.0, which depends on
      Flipper-Folly (~> 2.2)

FlipperKit (~> 0.54.0) was resolved to 0.54.0, which depends on
  FlipperKit/Core (= 0.54.0) was resolved to 0.54.0, which depends on
    Flipper (~> 0.54.0) was resolved to 0.54.0, which depends on
      Flipper-RSocket (~> 1.1) was resolved to 1.3.0, which depends on
        Flipper-Folly (~> 2.5)`

Using ({'Flipper-Folly' => '2.3.0'}) results in me getting the inital error again. Please help me fix this issue. Thank You

Kevon answered 10/2, 2021 at 21:37 Comment(0)
S
48

In my case, I had just had to update the repo.

pod install --repo-update

the above command worked for me.

Strut answered 31/3, 2021 at 7:29 Comment(2)
From the command output: out-of-date source repos which you can update with pod repo update or with pod install --repo-update.Feign
same error, made no differenceEpley
G
27

Delete Podfile.lock and run pod install. It will start working.Also update your cocoapods by running sudo gem install cocoapods

Gonfalon answered 11/2, 2021 at 8:25 Comment(2)
Don't do it never! Lock file needed for specify your packages versions.Maidy
You can safely do it. As pod install will generate a new, updated version of the Podfile.lock. It's like a ios version of rm -rf node_modules && npm installRichburg
H
15

as of today April 11, 2021 use_flipper!({ 'Flipper-Folly' => '2.3.0' }) no longer works. Instead you use, use_flipper!({ 'Flipper-Folly' => '2.5' }) if this won't work in the future either. Look into the error it will tell you which version to use.

Hungary answered 11/4, 2021 at 0:0 Comment(0)
R
7

For Mac M1 mates.

I just updates the repo.

arch -x86_64 pod install --repo-update

its worked

Rivy answered 23/4, 2022 at 7:43 Comment(0)
B
6

I have resolved the issue by running this command!

pod update RCT-Folly --no-repo-update

Brooklynese answered 8/5, 2023 at 7:9 Comment(0)
S
4

Remove the version with flipper so that it installs the latest available one on pod install.

So in pod file:

Change:

use_flipper!({ 'Flipper-Folly' => '2.3.0' })

to:

use_flipper!
Sequestration answered 5/10, 2021 at 2:44 Comment(0)
P
3
  1. Delete Podfile.lock

  2. Add to your Podfile

    use_flipper!({ 'Flipper-Folly' => '2.3.0' }) # update this part post_install do |installer|

    flipper_post_install(installer)

    end

  3. run pod install.

if your Podfile contains below code or something like this and its working successfully for one of your project but not working for others, which means

Your podfile.lock may contains above definition or working flavour of folly.

  use_flipper!
  post_install do |installer|
    flipper_post_install(installer)
    installer.pods_project.build_configurations.each do |config|
      config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
      config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
    end
  end
Polyptych answered 4/5, 2021 at 10:46 Comment(0)
D
3
arch -x86_64 pod install --repo-update

after running above command for the issue on M1 Chip Mac

CocoaPods could not find compatible versions for pod "FlipperKit": In Podfile: FlipperKit (= 0.125.0)

and you will see the result as per showing image enter image description here

Dicks answered 14/6, 2022 at 7:36 Comment(0)
O
0

For xcode 13 and react-native 0.66 (since the question is tagged with react-native), the only solution that worked for me is:

 react-native start --reset-cache
 rm -rf node_modules/
 rm -rf package-lock.json 
 cd ios && pod deintegrate
 cd .. && rm -rf ios/Podfile.lock 
 npm install
 npm audit fix
 react-native link
 cd ios && pod install
 cd .. && react-native run-ios

Source: https://github.com/facebook/react-native/issues/28408

Ornie answered 25/10, 2021 at 18:44 Comment(0)
J
0

I needed to go down one version before it, since the last one was 3 hours ago and obviously still not available in any repo.

Check this: https://github.com/facebook/flipper/releases And this: https://fbflipper.com/docs/getting-started/react-native/

Joannjoanna answered 9/2, 2022 at 20:18 Comment(0)
P
0

update:

version '2.6.10' works for me

use_flipper!({ 'Flipper-Folly' => '2.6.10' })
Pipette answered 22/6, 2023 at 17:55 Comment(0)
B
-1

For fast fix

Do update pod file :-

# use_flipper!
# post_install do |installer|
# flipper_post_install(installer)
# end
Blunt answered 9/5, 2021 at 5:53 Comment(0)
I
-1

Update 2022, May 27th:

npx pod-install --repo-update
Ilonailonka answered 27/5, 2022 at 13:7 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.