iOS - react-native-flipper includes FlipperKit, even in Release configuration

🐛 Bug Report

If you’re using react-native-flipper and do pod install, the included files assume you have FlipperKit installed.

However, if you have lines like these in your Podfile, FlipperKit will only be installed when your application is run in Debug configuration.

def add_flipper_pods!
  version = '~> 0.33.1'
  pod 'FlipperKit', version, :configuration => 'Debug'
  pod 'FlipperKit/FlipperKitLayoutPlugin', version, :configuration => 'Debug'
  pod 'FlipperKit/SKIOSNetworkPlugin', version, :configuration => 'Debug'
  pod 'FlipperKit/FlipperKitUserDefaultsPlugin', version, :configuration => 'Debug'
  pod 'FlipperKit/FlipperKitReactPlugin', version, :configuration => 'Debug'
end

Creating a release build will fail.

I upgraded from RN 0.61.5 to 0.62 and did the migration by hand, so I might’ve missed something that prevents this bug from happening on a fresh 0.62 install.

To Reproduce

1. Install react-native
2. npm i --save-dev react-native-flipper
3. Do pod install
4. Create a release build
5. Get this error:

Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_FlipperClient", referenced from:
      objc-class-ref in libreact-native-flipper.a(FlipperReactNativeJavaScriptPluginManager.o)

When react-native-flipper is removed and pod install is ran again, a release build will compile again.

Environment

iOS

[tr3v3r]

@mweststrate After upgrade to react-native v. 0.62.2 and react-native-flipper v. 0.37 the issue still presents 😭

As a workaround I had to disable auto-link for react-native-flipper for iOS. And manually add pods installation for react-native-flipper with Debug configutation

react-native-config.js

module.exports = {
  dependencies: {
    ...
    'react-native-flipper': {
      platforms: {
        ios: null,
      },
    },
    ...
  },
}

pods

pod 'react-native-flipper', :path => '../node_modules/react-native-flipper/react-native-flipper.podspec', :configuration => 'Debug'

I hope it helps.

[nvdnvd00]

yeah, it’s working but i think we need a solution, not workaround