useUser returns value null within AuthCheck children after signing out

[andrei-yanovich]

Reopening issue #155 , since AuthCheck is not entirely working.

Version info

React: 16.12

Firebase: 7.14

ReactFire: 2.0.3

Test case

https://codesandbox.io/s/pensive-fire-2v5qn?file=/src/config.js

Steps to reproduce

• Use a private component (App) as a child of AuthCheck and Login as a fallback
• Login using the form, App component with the user email should be rendered
• reload the page
• press sign out

Expected behavior

All children of AuthCheck shouldn't be rendered if there is no user logged in

Actual behavior

App component render fails with Cannot read property 'email' of null, because of useUser returning null. Happens only if an application is loaded with an active session.

[jhuleatt]

Thanks for reporting, @andrei-yanovich! We have a test to specifically guard against this, so I will revisit this test and see why it isn't catching this case:

reactfire/reactfire/auth/auth.test.tsx

Line 128 in 21b6702

it('always returns a user if inside an <AuthCheck> component', () => {

[jhuleatt]

And this test specifically tests the "loaded with an active session" case:

reactfire/reactfire/auth/auth.test.tsx

Line 103 in 21b6702

it('renders children if a user is logged in', async () => {

[jhuleatt]

Probably has to do with our mocking. The Auth Emulator can't come soon enough!

Still investigating.

[jhuleatt]

@jamesdaniels has been looking into similar Auth issues in AngularFire

[maxprilutskiy]

I faced the same issue yesterday. My guess is that the problem is in how the return value of the useUser hook is calculated. Usually, things like auth, currentUser, theme, etc. are passed through context, so when something changes react tree reacts appropriately, rebuilding stuff from top to bottom.

In this case, user value doesn't come from the context, so when it changes, it's then just being sent to the subscribers, instead of propagating through the react tree. Kind of a race condition.

For instance, if we declare a middleware like this

import React, { createContext, useContext, useEffect, useState } from 'react';
import { useUser } from 'reactfire';

const UserContext = createContext()

export const UserProvider = (props) => {
  const [user, setUser] = useState();
  const u = useUser();
  
  // I had to use JSON.stringify because useUser returns new instance on every call,
  // triggering an infinite update loop. It's bad and should be changed either.
  useEffect(() => setUser(u), [JSON.stringify(u)]) 

  return (
    <UserContext.Provider value={user}>
      {props.children}
    </UserContext.Provider>
  )
}

export const useUser2 = () => useContext(UserContext);

then the wrapper like this (maybe somewhere inside the <AuthCheck />?) would work as we expect it to work:

function InnerWrapper(props) {
  const u = useUser2()
  return u?.data ? props.children : null
}

That's pretty much what I was able to find out, hope this helps.