A while back, I asked my friend Arkadiy to help me debug Jumpy, but curiously he couldn’t even login. Arkadiy is my favorite kind of person - not only is he a brilliant engineer, but he’s in many ways a walking edge case. Wonder if your website works under a VPN with numerous ad-blockers and privacy-conscious plugins installed? This is the kind of user you need.

Evidently, my website did not work under these conditions. Specifically, Firebase Auth does not work unless the user enables 3rd party cookies. As Jumpy (initially, at least) is going to be a consumer-facing tool, this limitation is pretty alarming. Virtually every ad blocker prevents third party cookies (in 2019, over a quarter of internet traffic came from users with ad-blockers installed) - and some browsers like Brave do so as well.

Curiously, Google Sign In via Firebase is a completely separate product than the traditional Google API Sign in With Google. Why they can’t simply unite the two I’ll never know, but this is a guide to wrapping Firebase Auth around Sign in With Google. This way, we don’t have to redo any of our backend endpoints.

While the getting started guide and the basic integration docs work, they rely more on HTML processing and global script loading than modern javascript conventions. Integrating this SDK inside a modern React app proved to be slightly more challenging.


Google recommends doing something like the following.

<script src="" async defer></script>

Unfortunately, makes it messy for me later on down the road. Instead, I decided to initialize it entirely with Javascript, so that by the time I launch my main React App, googleApi is ready to go and loaded. The other benefit of doing it this way is that we can use the Context.Provider and Consumer model to access googleApi.

function loadGapiAndAfterwardsInitAuth() {
  const script = document.createElement('script')
  script.src = ''
  script.async = true
  script.defer = true
  script.onload = initAuth
  const meta = document.createElement('meta') = 'google-signin-client_id'
  meta.content = ''


Then, once platform.js is loaded and has fetched the regular google apis, we are ready to launch our react app.

The init function returns a promise, so it’s important to wait for the promise to load before saving an instance of googleAuth.

function initAuth() {
  window.gapi.load('auth2', function () {
      client_id: ''
    }).then(googleAuth => {
      if (googleAuth) {
          <GoogleAuthContext.Provider value={googleAuth}>
            <FirebaseContext.Provider value={new Firebase()}>
              <App />

We create the context as normal, with some helper methods like withGoogleAuth:

import React from 'react'

const GoogleAuthContext = React.createContext(null)

export const withGoogleAuth = Component => props => (
    {googleAuth => <Component {...props} googleApi={googleAuth} />}

export default GoogleAuthContext

One benefit to doing it this way is that we avoid the unnecessary /* global gapi */ that you’ll find with other implementations. Since everything is loaded into the react scope, we don’t need any mysterious global variables polluting up our namespace.

/* global gapi */
import React, { useContext, useEffect, useState } from 'react'
import Navbar from './navbar'
import DashboardPage from './dashboard'
import GoogleAuthContext from './googleauthContext'

function App(props) {
  const googleApi = useContext(GoogleAuthContext)
  const [isSignedIn, setIsSignedIn] = useState(false)

  useEffect(() => {
    // Needed to check if they're opening a new tab having already been signed in
    // The listener below only listens to *future* changes

    // Listen to future auth changes
    auth2.isSignedIn.listen((isLoggedIn) => {
  }, [])

  return (


        <Route exact path="/" component={IndexPage} />

        <Route exact path="/dashboard" component={DashboardPage} />
    </Router >

Since we’re using the google API to render our log in button, it’s important to call signin2 to re-render anytime the user logs out. Simply setting a conditional visibility doesn’t seem to work.

Lastly, we can conveniently pipe the data from gapi into Firebase with the signInWithCredential method, which then gives us access to all the data that we’d normally expect.

const Navbar = ({
}) => {
  const [menuOpen, setMenuOpen] = useState(false)
  const router = useRouter()
  const firebase = useContext(FirebaseContext)
  const googleApi = useContext(GoogleAuthContext)

  useEffect(() => {
    if (!isSignedIn && googleApi !== null) {
      window.gapi.load('signin2', function () {
        var opts = {
          longtitle: true,
          onfailure: signInWithGoogle,
          onsuccess: signInWithGoogle,
        gapi.signin2.render('loginButtonGoogle', opts)
  }, [isSignedIn])

  useEffect(() => {
    firebase.auth().onAuthStateChanged(async user => {
      if (user) {
        const token = await firebase.currentUser().getIdToken()
        const data = {
          displayName: user.displayName,
          photoURL: user.photoURL,
          userId: user.uid,
        // Send the data to your backend
  }, [])

  const signInWithGoogle = async (googleUser) => {
    const idToken = googleUser.getAuthResponse().id_token
    const credential = firebase.createCredential(idToken)

    await firebase.signInWithCredential(credential)


Some other useful links: