You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Netlify build fuils very often with `Error: Couldn't find temp query result for ""
Some have suggesed to add gatsby clean to our build command but I don't think that is a proper solution.
Even after "Clean and Retry from latest commit option" is still happening
Steps to reproduce
Build on netlify and gatsby.
A link to a reproduction repository
No response
Plugin version
3.8.1
More information about your build
I am building using the CLI
I am building using file-based configuration (netlify.toml)
What OS are you using?
Mac OS
Your netlify.toml file
`netlify.toml`
# Paste content of your `netlify.toml` file herecommand = "node scripts/create-env.js && cross-env GATSBY_COMMIT_REF=$COMMIT_REF yarn build"
Configuration
`gatsby-config.js` and options
# Paste content of your `gatsby-config.js` file, and/or command line options here. Check there is no private info in there.
{
resolve: "gatsby-plugin-netlify",
options: {
generateMatchPathRewrites: false,
headers: {
"/*": ["Referrer-Policy: strict-origin-when-cross-origin"],
},
},
}
Summary
Netlify build fuils very often with `Error: Couldn't find temp query result for ""
Some have suggesed to add gatsby clean to our build command but I don't think that is a proper solution.
Even after "Clean and Retry from latest commit option" is still happening
Steps to reproduce
Build on netlify and gatsby.
A link to a reproduction repository
No response
Plugin version
3.8.1
More information about your build
netlify.toml
)What OS are you using?
Mac OS
Your netlify.toml file
`netlify.toml`
Configuration
`gatsby-config.js` and options
Environment
Environment
Gatsby info
gatsby info
Your _redirects file
`_redirects`
# Paste content of your `_redirects` file here
Builds logs (or link to your logs)
Build logs
Function logs
Function logs
The text was updated successfully, but these errors were encountered: