Paul Darragh
Paul Darragh
Bumping this as we are seeing the same issue and are on 4.1.0, we did not see this issue on version 3.0.1. Any help would be appreciated
@swiftone tried reproducing this in a simple CRA and think it might actually be due to a useEffect that we were dependent on. Will respond back to this thread if...
@swiftone after getting some more time to investigate I have figured out what is causing the issue for our team, it was due to us passing the component the function...
@swiftone please report back if you did that as I would be interested in those results. I found an easy way to reproduce and check this was with adding a...