Just in case this helps someone else out there. We solved our issue by updating connected-react-router in our React project. There was an issue with that component, which meant a route was getting rendered twice. This was causing 2 hits to the parseHash function. The first hit would pass, but the second would fail, however this would be reported first and the code would produce the error message for the invalid token first.
4 Likes