We hope that flipper works well out of the box, but the software is a work in progress and problems will occur. Below are some known issues and steps you can take to try to resolve them.
Mac Desktop app
Flipper won't launch on Mac
- If the window is appearing, try opening the Chrome DevTools within Flipper. To do so, from the View menu select Toggle Developer Tools or press CMD+Option+I and check if there are any errors on the console.
- Launch Flipper from the command line using
/Applications/Flipper.app/Contents/MacOS/Flipper. This should give you some logs, that might be helpful when debugging.
~/.flipperand try relaunching Flipper.
- Delete Flipper from your applications folder and redownload Flipper.
- If you're using
yarn startto run from source, make sure all dependencies are installed correctly by running yarn install.
Flipper shows weird render artifacts
This is a long standing MacOS + Electron issue outside our control. In general restarting your computer fixes the problem.
For a quick, temporarily work around start Flipper with hardware acceleration disabled. Please note that this will consume a lot of CPU:
FLIPPER_DISABLE_GPU=1 open -a Flipper.
iOS Simulator missing from devices dropdown
- Check that
xcode-select -pshows the same XCode version that you're using. If not, see xcode-select for how to select the correct version.
No plugins showing up for your device
- Check your device isn't on the list of known incompatibilities.
- Make sure your version of Flipper is up to date.
- Make sure the mobile SDK you are using is relatively recent (<1 month old).
- Open Chrome dev tools within Flipper. To do so, from the View menu select Toggle Developer Tools or press CMD+Option+I and check if there are any errors on the console.
- Uninstall and reinstall the mobile app.
- Make sure the time and date are set correctly on your mobile device and desktop computer.
- If no app plugins are showing up, there may be a connectivity issue between Flipper and your app. Check connection issues to see if anything is failing.
The Flipper SDK includes an in-app connection diagnostics screen to help you diagnose problems.
<APP_PACKAGE> below with the package name of your app, e.g.
On a terminal, run the following:
This will only work if you added
FlipperDiagnosticActivity to your
AndroidManifest.xml. See getting started for help.
You'll need to manually add this ViewController to your app to see the in-app diagnostics.
The following devices are known to be incompatible or face issues with flipper:
- Physical iOS devices. Currently on iOS, only simulators are supported (Tracking Issue).
- Some Samsung devices (Tracking Issue).
- Genymotion emulators on Android 8+ are reported to have issues.
File an Issue
Still not working? File an issue on GitHub with the chrome DevTools logs and the output from the diagnostics screen, if relevant.
Exception from call site #4 bootstrap method
Build error after including the Flipper dependency:
This can happen because we include OkHttp3 as dependency which makes use of Java 8 features. There are two ways of dealing with this:
Enable Java 8 support
Add this to your Gradle config:
Exclude the OkHttp3 dependency
Alternatively, if you don't plan on making use of OkHttp, you can exclude the dependency from the build entirely:
This can occur when mixing different versions of FBJNI, a library we use to interact with native C++ code.
Speficially, this can happen when the versions
0.1.x are mixed. Version
0.1.0 of FBJNI
switched to using Google Prefab for distributing native artifacts,
which made the split into combined, "java-only" and "header" packages redundant and only requires
a single dependency in your projects.
When including both "fbjni-java-only:0.0.1" and "fbjni:0.1.0" in one project, you will now
duplicate class errors during the build process. You must ensure that only one of the two
versions is used in your entire dependency tree. Start by looking at
to see where the different version requirements come from. Then exclude the FBJNI dependency from
one of them, e.g.
Make sure the project is using the latest Flipper SDK.
When using Flipper with React Native, two devices should show up:
- The 'React Native' device. This is the "device" that talks to the Metro server and shows plugins that connect to or through Metro, such as the React DevTools, the Hermes Debugger and Metro logs.
- The device on which your app is running (like
iPhone 11). This is the device that Flipper connects to ADB / IDB. We primarily support emulators and USB connected devices.
Q: I don't see the 'React Native' device
- Make sure that the Metro server is running.
- Make sure you are on React Native 0.62 or higher.
- Verify that the
0.47.0or higher (using
yarn why @react-native-community/cli).
Q: I see my device / emulator, but I can't see the app
- Make sure you are running a debug build. Flipper only supports debug builds.
- If you are upgraded from RN < 0.62.2, make sure you've updated all the dependencies and build related files according to the upgrade helper. For example: https://react-native-community.github.io/upgrade-helper/?from=0.61.4&to=0.62.2
- If you upgraded, make sure you made a clean build:
cd android && ./gradlew clean,
cd iOS && pod install --repo-update
- For iOS, make sure it works on a simulator first
- (Unconfirmed) check the deployment info target in the XCode project settings. Target should be
Q: I see my app, but I don't see the external plugins I've installed
- Make sure you've installed the desktop part of the plugin (usually through "Manage plugins" in Flipper). If no plugins show up under "Manage plugins" > "Status", make sure you've selected your running device in the Flipper toolbar (and not "React Native").
- Make sure you've installed the app part of the plugin. Typically the installation instructions of the plugin itself need to be followed here.
- Make sure you've installed the latest version of
react-native-flipperin your app, and run
pod installin the
- Make sure you've restarted both Flipper and your app.
Q: On iOS it seems that the Flipper dependencies are compiled when making a release build
That is correct, the dependencies won't be actually included in the release (when using
react-native-flipper > 0.45), but sadly we can't exclude those dependencies from the build process.
Q: The React DevTools don't seem to connect
- Make sure there are no other instances of the React DevTools are running (For example a stand-alone version). Restart Flipper if needed after closing other tools.
- Make sure you have only one device running to connect to. If there are multiple devices, close them and try again (restart Flipper if needed).
- Make sure there is only one RN app running on the device
Q: How to select a specific element in the React DevTools?
- Trigger the debug menu on your RN app (you can use the button in the Flipper toolbar for that)
Show Inspector. Flipper will now follow the selection on your device.
Q: The Hermes Debugger does not connect
- Make sure the Hermes engine is enabled
- Make sure only one device with React Native is running
- Make sure there is only one RN app running on the device
- Make sure the React Native app is not in debug mode already (trigger dev menu, and make sure that
Remote JS Debuggingis not enabled).
iOS Build errors in React Native
First, make sure your cocoapods is up to date (
sudo gem install cocoapods), and that you are using the latest FlipperKit.
For inexplainable build errors, clone and verify if our reference project builds and runs locally. If it does, we recommend to compare the
ios/Podfile files with yours. If that doesn't yield anything, compare the
ios/Podfile.lock as well to verify any transitive pod dependencies need updating.
YogaKit.modulemap not found
- Make sure you are opening the
.xcodeworkspacedir when building from XCode, not the project file. Pods based projects should always be opened this way.
- Make sure you did run
cd ios && pod install.
- Restarting your machine seems to magically fix the issue for quite some people. This might especially be needed after doing an XCode upgrade.
- Make sure that the simulators are spawned by your current Xcode version. Force quite all simulators, run
sudo xcode-select --switch /Applications/Xcode.app(update path were necessary), and start simulators & Flipper again.
- Make sure the iOS build target version aligns with the podfile and target iOS 11. Example
- Verify XCode has enough permissions.
- More solutions might be found in this thread.
If you experience errors such as
Undefined symbol: associated type descriptor for FloatLiteralType or
Undefined symbol: __swift_FORCE_LOAD_$_swiftCompatibility50 after going through the Getting Started tutorial you must do as follows:
Open your project in Xcode;
Click in your project's name on the left side;
Make sure that you choose your project under
PROJECTon the screen that has been opened;
Go to the tab
LD_RUNPATH_SEARCH_PATHS(make sure that
Runpath Search Pathsand, in the dialog that opens, click on the plus button at the bottom-left corner and paste
Now search for
Library Search Pathsand, in the dialog that opens, add the following items:"$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)""$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)""$(inherited)"
Note: all of them should be added as
In the end it should look like this:
Now you can run your build normally.
Opting out from flipper (iOS)
Comment out the relevant lines in
ios/Podfile and run
cd ios && pod install again:
Disable Flipper on CI builds (iOS)
To speed up CI builds, Flipper can be disabled on CI environments by making the Flipper SDK inclusion conditional (this works on most CI providers, feel free to customize the environment variable):