akeohanePing
Results
2
comments of
akeohanePing
Circling back on this, I noticed the errors occur in react versions 16 and 17, but not in version 18. I'm curious if you all have any thoughts or insight...
Thanks for the bump. Yes, STRICT MODE was the issue here. Removing strict mode, resolved the issue