I keep running into the same issue every time I try to start my Gatsby development server. After I configured the gatsby-source-figma plugin in my gatsby-config.js file, the build process fails during the schema building phase.
The error message I’m getting is:
Missing onError handler for invocation 'building-schema', error was 'Error: Type with name "FigmaELLIPSE" does not exists'
This happens consistently and I can’t figure out what’s causing it. Has anyone else encountered this problem with the Figma source plugin? I’m wondering if there’s a configuration setting I’m missing or if this is a known bug with a workaround.
i dealt with this too! it’s a pain. try updating ur gatsby-source-figma plugin, Figma changed some stuff that messed with it. an update fixed it for me, hope it helps!
Had this exact error three months ago. It’s how the plugin handles node naming - the FigmaELLIPSE type gets auto-generated but Gatsby’s schema inference breaks when your data structure isn’t consistent. Clear your .cache folder completely, run gatsby clean, then restart dev server. That fixed it for me. Also check if you’ve got corrupted ellipses in your Figma file or ones missing properties. The plugin’s super sensitive to data issues and will tank your entire build over unexpected null values or broken shape data.
This happens when the Figma plugin can’t parse ellipse elements in your file into proper GraphQL types. I’ve hit this before with complex designs that had nested or grouped ellipses; the plugin just chokes on certain shapes and their properties. Check if you’ve got any ellipses with weird styling or unusual properties. Quick fix: add a filter function in your gatsby-config.js to exclude problematic ellipse nodes during data sourcing. Also, double-check your Figma file permissions; access issues sometimes show up as type errors.