navigation.js:173 Uncaught TypeError

[t2ca]

Updated my packages today and started getting this error when i click a link on my webpage.

navigation.js:173 Uncaught TypeError: Cannot read property 'getElementsByTagName' of null
    at navigation.js:173

  170 | if (document.title) {
  171 |   pageName = document.title
  172 | }
> 173 | const pageHeadings = document
  174 |   .getElementById(`gatsby-focus-wrapper`)
  175 |   .getElementsByTagName(`h1`)
  176 | if (pageHeadings && pageHeadings.length) {

[hatr1ck]

Same here

[heart-of-code]

Appears to have been introduced in this commit:
701222f

Reverting my Gatsby version to 2.18.24 seemed to resolve the crash, though I'm having issues with pages not loading any data when you click a gatsby link. Can't win 'em all I guess

[ehowey]

Just started hitting this too.

[marcysutton]

Same here, cc @madalynrose.

[Lc0rE]

I confirm to have hit this issue after upgrading to the latest 2.19.11 release.

[sidharthachatterjee]

Fix incoming

[ZeliosAriex]

Im having the same issue :(

[hupe1980]

Same here!

[mkidawa]

Experiencing the same issue :<

[shameer-rahman]

Same here

[sidharthachatterjee]

Fixed and published in gatsby@2.19.12

Apologies for this.

[garrison0]

I seem to be getting this exact issue even after updating Gatsby to 2.19.12

[t2ca]

Try rm -rf node_modules/
make sure you have the latest version and install again
The issue is with @reach/router: 1.3.0
So you want to make sure you have "@reach/router": "1.2.1"

[garrison0]

checked for both reach/router and gatsby versions in the dependencies, then removed node_modules and re-installed

still getting the error

[john-tipper]

Same error for me, I have 2.19.12 and @reach/router: 1.2.1, blown away node_modules and everything else associated with my project and the error is still occurring.

[jodiedoubleday]

Yea same issue for me, interestingly my project works fine until I start using Gatsby Image, then the problem occurs on my homepage only /pages/index

[kushal9291]

Same issue. Was working fine until I start using MDXRenderer (gatsby-plugin-mdx)

[legarams]

Having the same issue

[chamod-gamage]

Having the same issue appear on a specific set of pages. Same code works fine on a Mac but not on my Windows machine. Tried different versions of Gatsby.

[RobertDanielsson]

Having the same issue, "gatsby": "^2.19.19".

Edit: I fixed it. My components filename was "Search.js" and route was navigate("/search"). Renamed my file to search.js and it started working.

[grantmac]

Same issue "gatsby": "^2.19.12". Any work arounds as my Link is totally dead?

[LekoArts]

The original issue was solved and the reproduction steps mentioned here cannot reproduce it anymore. If you have further problems you can take a look at #21263 so that we don’t have duplicate issues. Thanks!

[kimicla]

Having the same issue, "gatsby": "^2.19.19".

Edit: I fixed it. My components filename was "Search.js" and route was navigate("/search"). Renamed my file to search.js and it started working.

I rename the file in page from Cart.js to cart.js. It works. Thank you.

[EduGomes18]

I try all the steps above but i still getting this issue D:, rename files to lowercase, put all files in the src/pages root, using gatsby clean and also deleting node_modules and yarn.lock, i don`t know what more can i do to solve this, someone have a diferent way?

[Tony221268]

still 100% getting this error

[huynhpeter]

Just started running into this issue as well