withAuthenticationRequired causing infinite loops when calling wrapped component's effect

Describe the problem

Since upgrading to 1.2.0 from 1.0.0, it seems that creating a ProtectedRoute using withAuthenticationRequired leads to infinite remounting of components.

I am using React 16.13.1, react-router-dom 5.2.

This problem does not happen with auth0-react 1.0.0

export const ProtectedRoute = ({
                                component,
                                ...args
                              }: {
  component: ComponentType;
  exact?: boolean;
  path: string;
}) => {
  const Comp = withAuthenticationRequired(component, {});
  // @ts-ignore
  return <Route {...args} render={(props) => <Comp {...props} />} />;
};

Usage that will cause it to break

// imagine this is inside a switch in react-router
<ProtectedRoute component={MyComponent} path="/whatever" />

// now this is our MyComponent, it calls an async thunk

function MyComponent() {
  const fetchResults = async () => {
    try {
      dispatch(someAsyncThunk());
    } catch (err) {
    }
  };

  useEffect(() => {
    fetchResults();
  }, []);

  return (<div>I will just keep calling my effect!</div>)
}

[dilhansarica]

It would be awesome to have a hook helper like useLoginRedirectEffect() to do somethings like this

const ProtectedRoute = ({
  component: Component,
}: {
  component: React.ComponentType;
}) => {
  const AuthMetadata = useSelector((state: State) => state.auth.entity);
  const { isAuthenticated, isLoading, loginWithRedirect } = useAuth0();
  const options = {
    loginOptions: buildLoginOptions(AuthMetadata),
  };
  const beforeRedirect = () => {
    if (!isAuthenticated) {
      localStorage.setItem(
        LOCALSTORAGE_ENUM.REDIRECT_URL,
        window.location.href,
      );
    }}
  const [ onRedirecting ] = useLoginRedirectEffect(options, beforeRedirect)
  return isAuthenticated ? <Component /> : onRedirecting();
};

[type]

My bad, I had an axios interceptor that got left in on accident in the App.jsx component that was using getAccessTokenSilently(). This was working okay with 1.0.0 but broke with 1.2.0. But not really a bug!