3df970a7d3
Summary: Adds troubleshooting infos for issues like https://github.com/facebook/flipper/issues/444 Reviewed By: passy Differential Revision: D15335814 fbshipit-source-id: 96969d61a6842c86123b77817059340fec38a665
21 lines
1.5 KiB
Markdown
21 lines
1.5 KiB
Markdown
---
|
|
id: debugging
|
|
title: Debugging
|
|
---
|
|
|
|
Flipper is built on Electron which itself is built on Chromium. This means we can debug Flipper using Chrome's developer tools. Flipper will also automatically install the React devtools extension allowing you to have better insight into what is going on in your plugin.
|
|
|
|
You can open the dev tools from the menu with `View` > `Toggle Developer Tools` or pressing ⌥⌘I on a Mac.
|
|
|
|
In addition to helping you with the JavaScript, the JS console will also display uncaught exceptions thrown from the client plugin in response to Flipper method calls.
|
|
|
|
## Plugin missing
|
|
|
|
If a plugin you created is not showing up there might be two potential classes of problems: Either there is a problem on the mobile side or on the desktop side. Understanding where the problem is rooted helps debugging it.
|
|
|
|
Click on "Plugin now showing" in the sidebar and see if your plugin is listed here. If it is not listed, the desktop side of the plugin is not loaded. One of the main reasons for this is that the plugin could not be compiled, due to some errors. Try launching Flipper from the Terminal to see some additional logs: `/Applications/Flipper.app/Contents/MacOS/Flipper`.
|
|
|
|
A common error here is `Error: fsevents unavailable (this watcher can only be used on Darwin)`. This can be fixed by installing watchman (`brew install watchman`).
|
|
|
|
If the plugin is listed in the desktop app, but still is not showing up in the sidebar, the mobile app is not announcing the plugin. In this case, make sure, to instantiate your plugin and add it to your FlipperClient.
|