Question 131177 in Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode – react-native iOS new scheme error: Undefined symbol: _OBJC_CLASS_$_FlipperClient

I added a new build configuration, Dev.Debug to my react-native project in xcode, duplicating the existing Debug configuration, and also added a corresponding scheme for the new configuration.

Now when I attempt to run the project with the new scheme I get the error:

Undefined symbol: _OBJC_CLASS_$_FlipperClient

Running the scheme that I duplicated works fine – the app installs, launches, and functions normally.

Is there any more configuration required after adding a new debug scheme?

Tags:

3

Answers


  1. Chosen as BEST ANSWER
    0

    I found that I needed to modify my podfile as follows:

    ...

target 'MyApp' do
  config = use_native_modules!
  
  # Add the project and build configurations
  project 'MyApp',
    'Dev.Debug' => :debug, # '{Build Configuration name}' => :{debug or release}
    'Debug' => :debug,
    'Dev.Release' => :release,
    'Release' => :release
...

use_flipper!({'Flipper' => '0.126.0', configurations: ['Debug', 'Dev.Debug']}) # Add the Build Configuration name (not scheme name)

...

  2. 0

    In my case I updated to react native: 0.70.* and Flipper to version 174 and had this error. Downgrading Flipper to 163 fixed the issue for me.

    More info here: https://github.com/facebook/flipper/issues/4278

    Login or Signup to reply.
  3. 0

    In recent versions of React Native, AppDelegate.mm has replaced the legacy Flipper initialisation code with RCTAppSetupPrepareApp(application); and I had forgotten to do so. This caused the issue for me. Fixing it solved the issue. See https://react-native-community.github.io/upgrade-helper/ for the diffs.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search