Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

React 18 StrictMode causes "AuthUI instance is deleted" error

Open
#172 4 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
firebase, javascript, react

Research direction

Start by locating the wrapper component's componentDidMount and componentWillUnmount implementations, then compare their cleanup behavior with the React 18 StrictMode lifecycle described here. Reproduce the issue in a local React 18 StrictMode app and verify that cleanup leaves the AuthUI instance usable and the UI renders without the deletion error.

Written by the indexing model from the issue text.

Description

When using react-firebaseui in React 18 with Strict Mode enabled and running a local dev server, the UI doesn’t render at all and produces this error in the console:

Uncaught (in promise) Error: AuthUI instance is deleted!

This is because of a change in behavior in Strict Mode to support concurrent features in React 18. Now components are mounted twice. See:

It seems the culprit is the deletion of the AuthUI instance when the component is unmounted. Reading the firebaseui documentation, it seems that this isn’t necessary to do, since the firebaseUiWidget property will either get the existing instance or create a new one.

I’ve ported the existing componentDidMount and componentWillUnmount code to a useEffect and removed the instance deletion, and used the modular v9 version of onAuthStateChanged. This seems to work for me:

useEffect(() => {
  let firebaseUiWidget: firebaseui.auth.AuthUI;
  let userSignedIn = false;
  let unregisterAuthObserver: ReturnType<typeof onAuthStateChanged>;

  // Get or Create a firebaseUI instance.
  firebaseUiWidget =
    firebaseui.auth.AuthUI.getInstance() ||
    new firebaseui.auth.AuthUI(firebaseAuth);

  if (uiConfig.signInFlow === "popup") firebaseUiWidget.reset();

  // We track the auth state to reset firebaseUi if the user signs out.
  unregisterAuthObserver = onAuthStateChanged(firebaseAuth, (user) => {
    if (!user && userSignedIn) firebaseUiWidget.reset();
    userSignedIn = !!user;
  });

  // Render the firebaseUi Widget.
  firebaseUiWidget.start("#" + ELEMENT_ID, uiConfig);

  return () => {
    unregisterAuthObserver();
    firebaseUiWidget.reset();
  };
}, [uiConfig]);

Is there something that I’m missing that would require the instance to be deleted entirely?

Dominant language
JavaScript
Stars
1.3k
Forks
246
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/firebaseui-web-react

All issues in firebase/firebaseui-web-react

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.