Layout graphql query data not being passed down to 404 page

[baseten]

Description

I have a graphql query in my layout, which is passing down data to all pages. The 404 page receives this data in development, but not in production.

Environment

Gatsby version: 1.9.52
Node.js version: 8.9.1
Operating System: Mac OS 10.11.6

Actual result

404 page not receiving layout graphql query data

Expected behavior

404 page should receive layout graphql query data as per other pages

Steps to reproduce

1. Add graphql query to src/layouts/index.js

2. Add src/pages/404.js component using data from this query

3. Run gatsby build followed by gatsby serve and navigate to non-existent page

[KyleAMathews]

Yeah, looks like we're not passing props into the 404 page here

gatsby/packages/gatsby/cache-dir/production-app.js

Line 168 in 3945d01

location: { pathname: `/404.html` },

Could you try adding ...props there and see if it fixes things for you? And if it does, PR the fix?

Check out the contribution instructions for setting up a local dev environment https://www.gatsbyjs.org/docs/how-to-contribute/#contributing

[nikolaik]

I ran in to the same issue and adding ...props did not do the trick as suggested by @KyleAMathews. I'm not too familiar with the code base, but looking at the surrounding code it seems that layoutProps is not set for 404 pages, is it not rendered as a child of a layout?

[kakadiadarpan]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub issues, we have to clean some of the old issues as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Gatsby version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[kakadiadarpan]

This issue is being closed because there hasn't been any activity for at least 30 days. Feel free to open a new one if you still experience this problem 👍