-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: The result of this StaticQuery could not be fetched. #26037
Comments
Same issue |
We recently shipped some changes to our static queries. Cc'ing @sidharthachatterjee to diagnose and help ya'll out! |
Same issue for me too. Works fine in develop locally, failing on netlify. Tried moving one of the queries into a hook but got the error on the hook instead |
Same here, failing on Vercel. UPDATE: Same bug when trying to access a plugin page on Gatsby website. |
Thank you @blainekasten @sidharthachatterjee - There is a typo in the URL to reproduce. The URL is: https://www.revelwell.com.au |
Thank you for the url @jamesaspinall and others. Can you try clearing On Netlify and other platforms, you should be able to do this by triggering a deploy that clears cache. Also, @jamesaspinall Can you try removing |
Thank you @sidharthachatterjee for the - Can you advice on the best version of Gatsby to be using as well. Also after removing the off-line package by following the instruction in the Gatsby Docs the error still persists after a Clear Cache & Redeploy on Netlify - Live here: https://www.revelwell.com.au
|
I'm able to confirm that clearing the npm cache in a Vercel deployment resolves this issue unless your project also uses |
@pygeek Thank you for confirming that. Clearing npm cache resolves babel loader cache which fixes one issue. The other issue is @jamaspy Do you have a yarn lock file? Any Netlify Build plugins that are active currently? Is your site open source? I'd be very glad to take a look. Feel free to DM me on thttps://twitter.com/chatsidhartha/ if it is private. |
@sidharthachatterjee issue should be visible here if you can help: https://5f2045202995cd0007604f23--rlntls-gatsby.netlify.app/ |
Thanks for your quick response. I was curious when we can we be expecting a fix? Is there something I can change locally in the meantime (other than removing gatsby-plugin-transition-link)? |
@abeaclark A fix is open in #26077 and should be out tonight or tomorrow. Removing the plugin at the moment is the way to go! |
Thank You @sidharthachatterjee @pieh for you support. I am blown away by the community here. THANK YOU. We removed the |
I'm getting the same error i'm not using Netlify and not using Contentful. I am using Prismic as CMS.
There is no other readable code to figure out where it's coming from. |
I am having the same issue using Netlify & NetlifyCMS. I followed @sidharthachatterjee advice and removed the gatsby-offline-plugin & service worker as well as caches, but the problem persists. Here are my dependencies:
Would love to help in any way I can to solve this issue! |
Can you try running |
Just published a fix that should make query result loading a lot more robust in Please upgrade to it, clear cache, run a build and let me know! |
Worked for me! Thanks heaps! |
Working here too, thanks! |
Installed |
@pygeek Without |
With |
@pygeek We're yet to fix |
@pygeek Let's open another issue for this? So that we can reduce confusion? |
@sidharthachatterjee is there another Issue or PR open to resolve the issue with gatsby-plugin-offline? I've updated to the latest packages available and still experiencing issues—it seems like gatsby-plugin-offline is generally not busting cache. |
Since the original issue was solved, I'll close this in favour of #26563 where also the issues about |
Description
Hi Guys,
I have had a Gatsby Project running perfectly fine for 3 months.
We are hosted on Netlify and using Contentful as the CMS.
As of Friday 24th July, I am getting the below error:
Here are my current package versions
Steps to reproduce
Expected result
Users should be able to navigate normally throughout the site
Actual result
Blank/White screens show and StaticQuery fails to resolve
Environment
The text was updated successfully, but these errors were encountered: