facebook/flipper

macos 14.3.1 xcode 15.3 'facebook::flipper::SocketCertificateProvider' (aka 'int') is not a function or function pointer

krmao opened this issue · 7 comments

krmao commented

🐛 Bug Report

after upgrade macos to 14.3.1, and xcode to 15.3, xcode build react native 0.72.4 with error

Called object type 'facebook::flipper::SocketCertificateProvider' (aka 'int') is not a function or function pointer

also have a apple bug report https://forums.developer.apple.com/forums/thread/747552

To Reproduce

upgrade macos to 14.3.1
upgrade xcode to 15.3
xcode build react-native 0.72.4 project

Environment

macos 14.3.1
xcode 15.3
react-native 0.72.4

Quick Fix

midify FlipperTransportTypes.h and add bellow code to line 11

#include <functional>
nstr commented

Same issue

tboba commented

Hi there, I believe this issue is already fixed, since this commit is already on main (I can see this import in the newest release of Flipper as well).
Because of that, I'd suggest to move the discussion of this error to the React Native repo (there are already some issues that addresses this error).

krmao commented

thanks, now we can't use 0.248.0 #5486

flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled(["Debug"], { 'Flipper' => '0.248.0' })


[!] CocoaPods could not find compatible versions for pod "FlipperKit":
  In Podfile:
    FlipperKit (= 0.248.0)

None of your spec sources contain a spec satisfying the dependency: `FlipperKit (= 0.248.0)`.

You have either:
 * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.
  • 👍3
tboba commented

@krmao Looks like Xcode has some issues with compiling the library. Unfortunately I can't do much, since I'm not the maintainer of Flipper 😅 But I see that there are issues with publishing it, since 0.233.0 version - https://cocoapods.org/pods/Flipper

krmao commented

Thanks for the reply, @tboba. Now I found a valid fix. Happy coding! facebook/react-native#43335 (comment)

  • 👍1