-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin appearing with empty dropdown, unable to load store #10
Comments
What version of relay are you using? I've seen this happen when the plugin can't connect to the relay store for some reason. Also is it on iOS or Android? |
Have the same issue too, the flipper logs report Running Relay 12, Flipper 0.108.0 and It appears to be connecting as expected, when starting the plugin I get I'm aso getting the same result debugging on a physical Android device. Any tips for debugging the connection? |
Found a solution, strangely using a dynamic Swapping the dynamic import out for a require works: if (__DEV__) {
require('react-native-flipper-relay-devtools').addPlugin();
} |
@akinncar are you getting |
Thanks for reporting the issue, I'll see if I can reproduce and find a fix in the next few days! |
not really
Thanks, let me know if you want more information or if I can help with something more. |
Hi experts, new to react-native world. I tried to follow the readme and have very thing setup. But when launching the app, getting this error message from the flipper debugger console: |
I had the same issues in my app. I published a new version of the plugin that fixes the |
I found a solution. Do not put this code in
|
I'm really excited about getting this to work, and feel like I've gotten most of it set up, but I must be missing something.
I've got flipper + react native working together, and I can use the React DevTools plugin as expected
I've added your plugin to my project, and have the following code running
Any idea what's going on there? If you've got a hunch I'm happy to dig in and fix something if need-be.
Thanks!
The text was updated successfully, but these errors were encountered: