thanks for submission @sumit194

I wasn't able to reproduce this error using barebones app w/ specified package versions. Can you post more details on auth API you are using(e.g. signInWithRedirect) + your router configuration?

@sumit194 The default restoreOriginalUri callback function uses history API from react-router-dom, have you included the module in your dependencies?

You can also override the default implementation by following this guide.

Hi @oleksandrpravosudko-okta below are the implementation of my Okta Auth component

const ProtectedRoute = ({ children, ...rest }) => (
  <Suspense fallback={<div>loading...</div>}>
    <OktaComponent {...rest}>{children}</OktaComponent>
  </Suspense>
);

const OktaProvider = (props) => {
  const history = useHistory();
  const oktaAuth = new OktaAuth({
    issuer: config.okta.issuer,
    clientId: config.okta.client_id,
    redirectUri: config.okta.redirect_uri,
    restoreOriginalUri: async (_, originalUri) => {
      history.replace(toRelativeUrl(originalUri, window.location.origin));
    },
  });
  return (
    <Security oktaAuth={oktaAuth}>
      <SecureRoute path="/">
        <ProtectedRoute {...props} />
      </SecureRoute>
      <Route path="/implicit/callback">
        <LoginCallback />
      </Route>
    </Security>
  );
};

Now it is working fine, but if I remove the restoreOriginalUri from the oktaAuth then it throws the above error in first load

@shuowu yes I have react-router-dom as a dependency in my project, and after overriding the restoreOriginalUrl method it is working fine, but that should work without overriding as well

@sumit194 Can you try to move the oktaAuth initialization outside of the OktaProvider? As it may end up with creating more than one oktaAuth instances, which is not expected and may cause weird errors.

@shuowu before it was like that only, but after getting this issue I have to move it inside the component to use the history in restoreOriginalUrl

@sumit194 The error looks like a module export issue, but I cannot tell how it relevant with override the restoreOriginalUrl callback. Can you try our official sample to see if you can repro the issue there?

@shuowu sure, I'll try that, also can you please explain more about the module export issue (any specific component at okta package side or project side)

@sumit194 I saw some related issues by searching the error (facebook/react#14484). You can check the details in the linked thread.

I believe @sumit194 is referring to circular dependencies with exports/imports.

For anyone still tracking this, I had this issue as well, and it was because my <Security> block was outside the <Router> block. After nesting <Security> inside <Router> the issue went away.

@sumit194 Does @radicand 's comment above help?

Also, the dependency of react-router has been removed from the <Security> component since version 5. You can also try migrate to the latest version, see the migration guide for details.

Close the issue for now, feel free to reopen it if the issue still exist.