Kinda new to this so probably missing something simple but thought, other beginners might face a similar challenge so here is my problem:

Basically I have protected route that contains a graphql query. When inspecting, it returns all the the instances (H3 tags in this case) as empty objects as if it was not allowed to read the data or something.

Here is my code, some help or pointers would be much appreciated! :) Oh and thanks a lot for this great starter!

import React from 'react';
import { StaticQuery, graphql } from 'gatsby';
import AuthUserContext from '../components/Session/AuthUserContext';
import withAuthorization from '../components/Session/withAuthorization';
import Layout from '../components/layout';

const WikiPage = () => (
  <Layout>
    <WikiPageContent />
  </Layout>
);

const authCondition = authUser => !!authUser;

const WikiPageContent = withAuthorization(authCondition)(() => (
  <StaticQuery
  query={graphql`
    query ArticleQuery {
      allDatoCmsArticle {
        edges {
          node {
            title
          }
        }
      }
    }
  `}
  render={data => (
  <AuthUserContext.Consumer>
    {authUser => (
      <div>
        <h1>Testing</h1>
        <div>
           {data.allDatoCmsArticle.edges.map(({ node: article }) => (
                   <h3>{data.allDatoCmsArticle.title}</h3>
           ))}
           </div>
      </div>
    )}
  </AuthUserContext.Consumer>
    )}
    />
  ));

export default WikiPage;

Tried using this and get the following errors.

Module not found: Error: Can't resolve 'core-js/features/symbol/iterator' in '/Users/max/Documents/Developer/Gatsby/playground/node_modules/@firebase/polyfill/dist'
 @ ./node_modules/@firebase/polyfill/dist/index.esm.js 9:0-42
 @ ./node_modules/firebase/app/dist/index.cjs.js
 @ ./src/components/Layout.js
 @ ./src/pages/account.js
 @ ./.cache/sync-requires.js
 @ ./.cache/app.js
 @ multi event-source-polyfill (webpack)-hot-middleware/client.js?path=/__webpack_hmr&reload=true&overlay=false ./.cache/app
ℹ ｢wdm｣: Failed to compile.

There have been updates to the gatsby monorepo:

• • The dependency gatsby was updated from 2.0.58 to 2.0.59.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

First of all I would like to thank you for the great work.

In dev mode i have the following error in the console:

Does anyone have a solution to this problem?

The devDependency prettier was updated from 1.15.2 to 1.15.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency firebase was updated from 5.5.6 to 5.5.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

firebase is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby was updated from 2.0.58 to 2.0.59.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency gatsby-plugin-react-helmet was updated from 3.0.0 to 3.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby-plugin-react-helmet is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency gatsby was updated from 2.0.35 to 2.0.36.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby was updated from 2.0.58 to 2.0.59.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency firebase was updated from 5.5.9 to 5.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

firebase is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

After pinning to 2.0.34 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

Originally posted by @Greenkeeper in #20 (comment)

I followed the instructions, when running gatsby develop, the build failed and i needed to run npm install --save react-router-dom
After that it would successfully compile.
after loading local host in my browser, when i click Sign In it loads a blank page.
How do i resolve this issue?

Hi,

i just installed this project on node v8.10.0 and updated the credentials in src/components/Firebase/firebase.js.

i am getting an this error whenever i click a link…

TypeError: this.listener is not a function

any idea why this happens?

I am a new developer so this could be something simple but I am not able to send a validation email after successfully signing up a user. I have searched through the code as much as possible but I don't where or how I can declare a Continue URL

Tried following the tutorial steps but keep getting a CORS error on any page that uses firebase in local development. I attempted to create a proxy server following the gatsby api proxy docs but not sure what to set the middleware path to since there is no direct 'api' route and the firebase auth is a wrapper for the pages. Also tried adding "proxy": "http://localhost:8000" in my package.json. How do you get past this CORS issue in development?

Access to XMLHttpRequest at 'https://www.googleapis.com/identitytoolkit/v3/********' from origin 'http://localhost:8000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header has a value 'https://localhost:8000' that is not equal to the supplied origin.

I keep getting this HPM Error when i try to visit my page after running Gatsby Develop. The project compiles Successfully but then I get this error in the browser

error occurred while trying to proxy to: localhost:8000/

and this in the terminal

error [HPM] Error occurred while trying to proxy request / from localhost:8000 to http://localhost:4000 (ECONNREFUSED)

once I remove this from the
-config.js file it works and the pages generated in the browser:

module.exports = {
    developMiddleware: app => {
        app.use(
            proxy({
                target: "http://localhost:4000",
            })
        )
    },
}

However, I then get this error in the terminal :

Error loading a result for the page query in "/404.html". Query was not run and no cached result was found.
Page not found /404.html

Even though I get this error the pages work and the project Compiles successfully.

I Really want to know how to fix the first error without getting rid of the proxy in the config file.

Here is my repo:
https://github.com/thelovesmith/Island-Stream-Web-MVP

The dependency gatsby was updated from 2.0.31 to 2.0.32.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency prettier was updated from 1.14.3 to 1.15.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi Robin, thanks for this great project. It inspired me a lot.

When trying the live demo, I encountered TypeError: Cannot read property 'email' of null in this link

I'm not sure if withAuthorization(authCondition) running correctly in that page, cmiiw.

I'm afk to running it in my machine, btw.

Cheers

HI, I have done the steps below but run into the following error when I try to sign in or register.

Firebase: Firebase App named '[DEFAULT]' already exists (app/duplicate-app).
▶ 2 stack frames were collapsed.
new Firebase
C:/Users/arhoy/OneDrive/Desktop/web-development/playground/gatsby/react-gatsby-firebase-authentication/src/components/Firebase/firebase.js:76
  73 |            }
  74 | 
  75 |            // merge auth and db user
> 76 |            authUser = {
  77 |              uid: authUser.uid,
  78 |              email: authUser.email,
  79 |              emailVerified: authUser.emailVerified,
View compiled
getFirebase
C:/Users/arhoy/OneDrive/Desktop/web-development/playground/gatsby/react-gatsby-firebase-authentication/src/components/Firebase/firebase.js:104
  101 |   messages = () => this.db.ref('messages');
  102 | }
  103 | 
> 104 | let firebase;
  105 | 
  106 | function getFirebase(app, auth, database) {
  107 |   if (!firebase) {
View compiled
(anonymous function)
C:/Users/arhoy/OneDrive/Desktop/web-development/playground/gatsby/react-gatsby-firebase-authentication/src/components/layout.js:1
> 1 | import React, { Component, Fragment } from 'react';
  2 | 
  3 | import Navigation from './Navigation';
  4 | import getFirebase, { FirebaseContext } from './Firebase';

I am not sure what I am doing wrong, I have set up my ENV variables from Firebase and all that.

Thank you

There have been updates to the gatsby monorepo:

• • The dependency gatsby was updated from 2.0.58 to 2.0.59.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

node: 8.11.3
npm: 5.6.0
yarn: 1.6.0
gatsby: 2.4.3

I do:

yarn install
gatsby develop

And get a lot errors:

ℹ ｢wdm｣: Compiling...
 ERROR  Failed to compile with 6 errors                                                                                        07:44:05

This relative module was not found:

* ../components/Layout in ./src/pages/account.js, ./src/pages/home.js and 4 others
✖ ｢wdm｣: 
ERROR in ./src/pages/account.js
Module not found: Error: Can't resolve '../components/Layout' in '/media/sdb1/dev/rnd/experiments/gatsby-firebase-authentication/src/pages'
 @ ./src/pages/account.js 10:0-42 65:29-35
 @ ./.cache/sync-requires.js
 @ ./.cache/app.js
 @ multi ./node_modules/react-hot-loader/patch.js (webpack)-hot-middleware/client.js?path=http://localhost:8000/__webpack_hmr&reload=true&overlay=false ./.cache/app

ERROR in ./src/pages/home.js
Module not found: Error: Can't resolve '../components/Layout' in '/media/sdb1/dev/rnd/experiments/gatsby-firebase-authentication/src/pages'
 @ ./src/pages/home.js 16:0-42 136:29-35
 @ ./.cache/sync-requires.js
 @ ./.cache/app.js
 @ multi ./node_modules/react-hot-loader/patch.js (webpack)-hot-middleware/client.js?path=http://localhost:8000/__webpack_hmr&reload=true&overlay=false ./.cache/app

ERROR in ./src/pages/index.js
Module not found: Error: Can't resolve '../components/Layout' in '/media/sdb1/dev/rnd/experiments/gatsby-firebase-authentication/src/pages'
 @ ./src/pages/index.js 10:0-42 35:29-35
 @ ./.cache/sync-requires.js
 @ ./.cache/app.js
 @ multi ./node_modules/react-hot-loader/patch.js (webpack)-hot-middleware/client.js?path=http://localhost:8000/__webpack_hmr&reload=true&overlay=false ./.cache/app

ERROR in ./src/pages/pw-forget.js
Module not found: Error: Can't resolve '../components/Layout' in '/media/sdb1/dev/rnd/experiments/gatsby-firebase-authentication/src/pages'
 @ ./src/pages/pw-forget.js 10:0-42 36:29-35
 @ ./.cache/sync-requires.js
 @ ./.cache/app.js
 @ multi ./node_modules/react-hot-loader/patch.js (webpack)-hot-middleware/client.js?path=http://localhost:8000/__webpack_hmr&reload=true&overlay=false ./.cache/app

ERROR in ./src/pages/signin.js
Module not found: Error: Can't resolve '../components/Layout' in '/media/sdb1/dev/rnd/experiments/gatsby-firebase-authentication/src/pages'
 @ ./src/pages/signin.js 10:0-42 50:29-35
 @ ./.cache/sync-requires.js
 @ ./.cache/app.js
 @ multi ./node_modules/react-hot-loader/patch.js (webpack)-hot-middleware/client.js?path=http://localhost:8000/__webpack_hmr&reload=true&overlay=false ./.cache/app

ERROR in ./src/pages/signup.js
Module not found: Error: Can't resolve '../components/Layout' in '/media/sdb1/dev/rnd/experiments/gatsby-firebase-authentication/src/pages'
 @ ./src/pages/signup.js 10:0-42 36:29-35
 @ ./.cache/sync-requires.js
 @ ./.cache/app.js
 @ multi ./node_modules/react-hot-loader/patch.js (webpack)-hot-middleware/client.js?path=http://localhost:8000/__webpack_hmr&reload=true&overlay=false ./.cache/app
ℹ ｢wdm｣: Failed to compile.

The dependency firebase was updated from 5.5.5 to 5.5.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

firebase is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency gatsby was updated from 2.0.39 to 2.0.40.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hello!

This is really great, thanks for building!

Ran into a small issue today while building from the starter. When you reload the page you'll loose the firebase user and hence any content behind the auth. If you navigate to a different page and then back it'll re-appear.

Thanks again.

There have been updates to the react monorepo:

• • The dependency react was updated from 16.6.0 to 16.6.1.

• The dependency react-dom was updated from 16.6.0 to 16.6.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency gatsby was updated from 2.0.33 to 2.0.34.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The link on the Star Repository on the live demo for the GatsbyJS Starter sends to a different repo. I tried looking where the link was being made and send a PR to fix but see no sign of anywhere in the code on this repo where the footer on that demo comes from.

Just a head's up: I could not build on Node 11.*
No issues once I downgraded to 10.13

Best!

The dependency gatsby was updated from 2.0.38 to 2.0.39.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency gatsby was updated from 2.0.34 to 2.0.35.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby was updated from 2.0.58 to 2.0.59.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby was updated from 2.0.58 to 2.0.59.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴