Gatsby: -warn- Multiple node fields resolve to the same GraphQL field

[MauriceOppenberger]

might be banal but I am getting this error message when compiling and deploying by gatsby site. That site is still being built but I can't figure out what causes the error message

Message ---
warn Multiple node fields resolve to the same GraphQL field wordpress__acf_pages.acf.landingbackground - [landingbackground, landingbackground___NODE]. Gatsby will use
landingbackground___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__acf_pages.acf.contactbackground - [contactbackground, contactbackground___NODE]. Gatsby will use
contactbackground___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__acf_pages.acf.exterioricon - [exterioricon, exterioricon___NODE]. Gatsby will use exterioricon___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__acf_pages.acf.interioricon - [interioricon, interioricon___NODE]. Gatsby will use interioricon___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__acf_pages.acf.additionalicon - [additionalicon, additionalicon___NODE]. Gatsby will use
warn Multiple node fields resolve to the same GraphQL field wordpress__PAGE.acf.landingbackground - [landingbackground, landingbackground___NODE]. Gatsby will use
landingbackground___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__PAGE.acf.contactbackground - [contactbackground, contactbackground___NODE]. Gatsby will use
contactbackground___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__PAGE.acf.exterioricon - [exterioricon, exterioricon___NODE]. Gatsby will use exterioricon___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__PAGE.acf.interioricon - [interioricon, interioricon___NODE]. Gatsby will use interioricon___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__PAGE.acf.additionalicon - [additionalicon, additionalicon___NODE]. Gatsby will use additionalicon___NODE.
warn Multiple node fields resolve to the same GraphQL field wordpress__wp_media.guid - [guid___NODE, guid]. Gatsby will use guid___NODE.

my query---

query HomePageQuery {
wordpressPage(title: { eq: "Homepage" }) {
acf {
landingbackground {
localFile {
url
childImageSharp {
fluid(quality: 100, maxWidth: 2000) {
...GatsbyImageSharpFluid_withWebp
src
}
}
}
}
contactbackground {
localFile {
url
childImageSharp {
fluid(quality: 100, maxWidth: 1800) {
...GatsbyImageSharpFluid_withWebp
src
}
}
}
}
exterioricon {
localFile {
url
}
}
interioricon {
localFile {
url
}
}
additionalicon {
localFile {
url
}
}
}
}
}

any suggestions?

Summary

Relevant information

Environment (if relevant)

File contents (if changed)

gatsby-config.js: N/A
package.json: N/A
gatsby-node.js: N/A
gatsby-browser.js: N/A
gatsby-ssr.js: N/A

[LekoArts]

Thank you for opening this!

These warnings can sometimes occur in certain situations with the wordpress source plugin but they shouldn't cause any troubles. So for now: Save to ignore.

If you want you can try WPGraphQL: https://www.wpgraphql.com/
It's a great way to use Gatsby with Wordpress.

We're marking this issue as answered and closing it for now but please feel free to comment here if you would like to continue this discussion. We also recommend heading over to our communities if you have questions that are not bug reports or feature requests. We hope we managed to help and thank you for using Gatsby!

[havietduc91]

Hi @LekoArts,

I'm facing the same issue here with Airtable,

warn Multiple node fields resolve to the same GraphQL field `Airtable.data.Project` - [`Project`, `Project___NODE`]. Gatsby will use `Project___NODE`.
warn Multiple node fields resolve to the same GraphQL field `Airtable.data.Publication` - [`Publication`, `Publication___NODE`]. Gatsby will use `Publication___NODE`.

Could you please let me know the solution to resolve it, many thanks

[szimek]

I've got the same issue with Contentstack (https://www.gatsbyjs.org/packages/gatsby-source-contentstack/):

warn Multiple node fields resolve to the same GraphQL field `Contentstack_post.author` - [`author`, `author___NODE`]. Gatsby will use `author___NODE`.
warn Multiple node fields resolve to the same GraphQL field `Contentstack_post.category` - [`category`, `category___NODE`]. Gatsby will use `category___NODE`.
warn Multiple node fields resolve to the same GraphQL field `Contentstack_post.featured_image` - [`featured_image`, `featured_image___NODE`]. Gatsby will use
...
warn There are conflicting field types in your data.

Could it have any impact on createSchemaCustomization and createTypes call?

[selenecodes]

I have the same issue with Strapi, in specific the gatsby-source-strapi plugin.

warn Multiple node fields resolve to the same GraphQL field `StrapiCategory.articles.image` - [`image`, `image___NODE`]. Gatsby will use `image___NODE`.
warn Multiple node fields resolve to the same GraphQL field `StrapiArticle.image` - [`image`, `image___NODE`]. Gatsby will use `image___NODE`.

[pjamieson]

Closed because?

[kulahin]

The decision is obvious enough: try not to use the same field names for different types.
I had such warnings in my Gatsby+Wordpress site:
warn Multiple node fields resolve to the same GraphQL field wordpress__wp_event.acf.image -
warn Multiple node fields resolve to the same GraphQL field wordpress__wp_city.acf.image -
warn Multiple node fields resolve to the same GraphQL field wordpress__acf_event.acf.image -
warn Multiple node fields resolve to the same GraphQL field wordpress__acf_city.acf.image -
warn There are conflicting field types in your data.
When I changed the image field name for both types to event_image and city_image the warnings had gone away.
The only issue is that I don't understand why Gatsby behaves so strange...