Please trigger a setState() to activate Lucid devtool.
See original GitHub issueDescribe the bug I am not sure what is meant by this error message. I do have React devtools installed and working just fine.
To Reproduce Hard to know, I suppose it’s some environment issue since no one else is reporting it.
The app is running React 16.7.0-alpha.2 in development mode. There is react-apollo 2.2.4.
I don’t use Redux, so if the setState is somehow related to that, it should be mentioned somewhere.
Expected behavior It should show the promised wow UI 😃
Screenshots

Desktop (please complete the following information):
- OS: Windows 10 x64
- Browser chrome
- Version 71
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (7 by maintainers)
Top Results From Across the Web
How can I wait for setState to finish before triggering a function ...
I don't want to trigger the findRoutes() function when unrelated state is updated. Please see code snippet below: handleFormSubmit: function( ...
Read more >Everything you need to know about setState() - Medium
This method is called with the new props passed as an argument. To use setState() here it is better to check if the...
Read more >Lucid Dreaming: Techniques, Benefits, and Cautions
Lucid dreams may potentially reduce nightmares, relieve anxiety, and improve motor skills and creativity. Use caution if you have a sleep or mental...
Read more >How to Lucid Dream | Sleep Foundation
In lucid dreams, we're aware of the fact that we're dreaming. ... easily once you fall asleep, which in turn can help trigger...
Read more >Lucid Dreams: Definition, Benefits, Dangers, How to Do It
The same part of your brain turns active whether you imagine the movements while awake or run through them during a lucid dream....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hey everyone, I just merged a few changes. These new changes should be able to get rid of the circular JSON error while still keeping information about properties of a component. If you want the changes right away then you can manually add Lucid to your browser or wait for the changes to be push to the chrome store but it takes some time to get it reviewed. Please give it a try and let me know if anyone still gets this error. Thank you.
I am seeing the same page on our app which is React 16+ and is using graphql. But I have a different error.