React Firebase Auth Persistence with Local Storage - Robin Wieruch

Previously, we implemented authentication for this Firebase in React application. Along the way, we added authorization with roles. You may have experienced a flicker every time you reload/refresh your browser, because the application doesn’t know from the start if a user is authenticated or not since the authenticated user is null. It will happen until Firebase figures out there is an authenticated user and calls the function in the listener of the authentication higher-order component:

After the Firebase authentication listener is invoked for the first time, the authenticated user may be there, because Firebase has its internal state for auth persistence. Also, the routes are made visible in the Navigation component due to the authenticated user being there now. While it’s good that Firebase keeps the state of the authenticated user, the UI glitch in the beginning hurts the user experience. Let’s avoid this using the browser’s local storage for the authenticated user:

Every time Firebase’s listener is invoked, the authenticated user is not only stored in the local state, ready to be passed to React’s Context API, but it’s also stored in the browser’s local storage. You can use the local storage’s API with setItem and removeItem to store and delete something identified by a key. You also need to format the authenticated user to JSON before you can put it into the local storage of the browser.

The flicker is still there, because we’re not really taking advantage of having the authenticated user earlier at our disposal. Let’s change this by retrieving it from the local storage in the higher-order component’s constructor earlier:

If there is no auth user in the local storage, the local state will stay null and everything will remain as before. However, if the authenticated user is in the local storage because it was stored via our Firebase listener’s function, we can use it in the component’s constructor. Since the format of the authenticated user in the local storage is JSON, we need to transform it into a JavaScript object again. Ultimately, someone using our application can refresh the browser, but also close the browser/tab and open it after a while, and it will still see them as an authenticated user.

Try the application again and verify that the flicker is gone. Also all the conditional routes and pages that are protected with a conditional rendering (e.g. Navigation component) or authorization (e.g. HomePage component) should be there immediately. The authentication higher-order component can pass the authenticated user with its first render via React’s Context API to all other components.