Closed theogravity closed 3 months ago
Hello. Thanks for reporting this.
Where exactly is this error being reported? Is this from the Expo CLI or in the browser console when the dev tools are open?
This is when I select the plugin from the CLI after hitting shift + M (in macOS)
When you say this:
It doesn't prevent me from running the redux devtools plugin, though
Does this mean that you are able to use this devtools plugin even though you're getting this error? Does it stop you doing anything?
Works without problems
Ok. In that case I'm going to close this issue. If you're able to reproduce the issue and find out why it's happening then feel free to open a new issue with details about it and we can try to fix it.
Thanks again.
The issue does happen, it's reproducible on my machine, just don't know what causes it. It doesn't seem to interfere with my ability to use the plugin.
I know the issue is happening on your machine, but a proper reproduction would allow us to see the issue on other machines.
If you can figure out the root cause then feel free to open a new issue. A new issue is easier for me to find than a comment on a closed issue.
Just reporting this in case you haven't seen this on your own machine:
The built-in react devtools run fine (and doesn't emit that error) and it's also via this port as well, so it might not be an issue.
It doesn't prevent me from running the redux devtools plugin, though.
My setup follows the RTK example you have.