Stack Trace: TypeError: Cannot Read Properties of Undefined (Reading 'Name')

10 replies

Last updated: Apr 14, 2022

I've inherited a project and running into an issue when attempting to create a new document. I get the following error message:

TypeError: Cannot read properties of undefined (reading 'name')

. This is only happening when creating a new document of this type, but not when opening existing documents. I've even commented out most of the fields except for title & slug, and the issue is persistent
Stack Trace:

TypeError: Cannot read properties of undefined (reading 'name')
    at resolveEnabledActions (/static/js/app.bundle.js:89193:70)
    at isActionEnabled (/static/js/app.bundle.js:89197:47)
    at resolveDocumentActions (/static/js/app.bundle.js:554716:52)
    at <http://localhost:3333/static/js/app.bundle.js:554446:77>
    at mountMemo (/static/js/vendor.bundle.js:18255:19)
    at Object.useMemo (/static/js/vendor.bundle.js:18551:16)
    at useMemo (/static/js/vendor.bundle.js:2408:21)
    at <http://localhost:3333/static/js/app.bundle.js:554446:36>
    at renderWithHooks (/static/js/vendor.bundle.js:17616:18)
    at updateFunctionComponent (/static/js/vendor.bundle.js:19847:20)

Component Stack:

in StructureError (created by DeskToolRoot)
    in DeskToolRoot (created by RenderTool)
    in ErrorBoundary (created by RenderTool)
    in RenderTool (created by SchemaErrorReporter)
    in RouteScope (created by SchemaErrorReporter)
    in div (created by styled.div)
    in styled.div (created by ForwardRef(Box))
    in ForwardRef(Box) (created by Styled(Component))
    in Styled(Component) (created by ForwardRef(Flex))
    in ForwardRef(Flex) (created by Styled(Component))
    in Styled(Component) (created by SchemaErrorReporter)
    in div (created by styled.div)
    in styled.div (created by ForwardRef(Box))
    in ForwardRef(Box) (created by Styled(Component))
    in Styled(Component) (created by ForwardRef(Flex))
    in ForwardRef(Flex) (created by Styled(Component))
    in Styled(Component) (created by SchemaErrorReporter)
    in div (created by styled.div)
    in styled.div (created by ForwardRef(Box))
    in ForwardRef(Box) (created by Styled(Component))
    in Styled(Component) (created by ForwardRef(Flex))
    in ForwardRef(Flex) (created by Styled(Component))
    in Styled(Component) (created by SchemaErrorReporter)
    in SchemaErrorReporter (created by DefaultLayout)
    in DefaultLayout (created by DefaultLayoutRoot)
    in RouterProvider (created by DefaultLayoutRoot)
    in LoginWrapper (created by NormalizedLoginWrapper)
    in NormalizedLoginWrapper (created by DefaultLayoutRoot)
    in DefaultLayoutRoot (created by AppProvider)
    in div (created by styled.div)
    in styled.div (created by ForwardRef(Box))
    in ForwardRef(Box) (created by Styled(Component))
    in Styled(Component) (created by ForwardRef(Card))
    in Fe (created by ThemeProvider)
    in ThemeProvider (created by ThemeColorProvider)
    in ThemeColorProvider (created by ForwardRef(Card))
    in ForwardRef(Card) (created by Styled(Component))
    in Styled(Component) (created by AppProvider)
    in SnackbarProvider (created by AppProvider)
    in ToastProvider (created by AppProvider)
    in LayerProvider (created by AppProvider)
    in PortalProvider (created by AppProvider)
    in UserColorManagerProvider (created by AppProvider)
    in AppProvider (created by SanityRoot)
    in Fe (created by ThemeProvider)
    in ThemeProvider (created by SanityRoot)
    in ZIndexProvider (created by SanityRoot)
    in SanityRoot
    in AppContainer

AI Update

Based on the error you're seeing and the solution found in the Sanity community, this TypeError: Cannot read properties of undefined (reading 'name') error that occurs specifically when creating new documents (but not when opening existing ones) is typically caused by outdated or incompatible Structure Builder syntax or custom document actions with missing properties.

The error is happening in the resolveEnabledActions and resolveDocumentActions functions, which means there's an issue with how document actions are being configured in your Structure Builder setup.

The Solution

The person who originally posted this exact issue found that their Structure Builder syntax was out of date. After refactoring the structure builder configuration to use current syntax, the problem was resolved.

Troubleshooting Steps

1. Check for custom document actions: Look in your project for any custom document actions configuration. If document actions are defined but have a missing or undefined name property, this will cause the exact error you're seeing. Document actions should always have a name property defined.

2. Review your Structure Builder: If you're using Structure Builder (typically in a deskStructure.js or similar file), check for deprecated syntax patterns. Common issues include:

Outdated .views() configuration
Improperly configured document lists
Missing or malformed action definitions

3. Temporarily remove Structure Builder: To isolate the issue, try commenting out the Structure Builder configuration in your sanity.config.js (or sanity.json for v2). If the error disappears, you know it's definitely a Structure Builder issue.

4. Standard Node.js troubleshooting: Delete node_modules, remove your lock file (package-lock.json or yarn.lock), and reinstall dependencies. Sometimes package version mismatches can cause these issues.

5. Check for custom schema types: Since the error persists even with minimal fields, verify that any custom types referenced in your schema (like figure, custom objects, or references) are properly defined and don't have their own action configurations that might be problematic.

Why This Happens

The key insight is that this error happens during document creation because that's when Sanity tries to determine which actions (publish, unpublish, delete, duplicate, etc.) should be available for the new document. It's encountering something with a missing name property in that resolution process.

Since existing documents open fine, the issue is specifically in how the Studio is trying to resolve available actions for a new document of this type. This strongly points to either custom document actions or Structure Builder configuration that's using outdated syntax or has a configuration error.

The most common fix is refactoring your Structure Builder to use current Sanity v3 syntax if you're on an older version, or checking any custom document actions to ensure they all have proper name properties defined. In inherited projects especially, it's worth checking if the syntax matches the version of Sanity Studio you're actually running.

user U

Hi Julia!
This is the structure builder for it:

export const ProductsMenuItem = S.listItem()
  .title("Products")
  .icon(BsTag)
  .child(
    S.list()
      .title("Products")
      .items([
        S.listItem()
          .title("Products")
          .schemaType("product")
          .child(
            S.documentTypeList("product")
              .title("Products")
              .child((documentId) =>
                S.document()
                  .documentId(documentId)
                  .views([
                    S.view.form().icon(FiEdit),
                    S.view
                      .component(IframePreview)
                      .options({ previewURL })
                      .title("Web Preview")
                      .icon(BsEye),
                  ])
              )
          )
          .icon(BsTag),
        S.listItem()
          .title("Collections")
          .schemaType("collection")
          .child(
            S.documentTypeList("collection")
              .title("Collections")
              .child((documentId) => S.document().documentId(documentId))
          )
          .icon(BsGrid),
        S.listItem()
          .title("Categories")
          .schemaType("category")
          .child(
            S.documentTypeList("category")
              .title("Categories")
              .child((documentId) => S.document().documentId(documentId))
          )
          .icon(BsCardList),
        S.listItem()
          .title("Shared Product Copy")
          .schemaType("productCopy")
          .child(
            S.documentTypeList("productCopy")
              .title("Shared Product Copy")
              .child((documentId) => S.document().documentId(documentId))
          )
          .icon(BsCollection),
      ])
  );

and this is the schema:

export default {
  name: "collection",
  title: "Product Collection",
  type: "document",
  fields: [
    {
      name: "title",
      title: "Title",
      type: "string",
    },
    {
      name: "slug",
      title: "Slug",
      type: "slug",
      options: {
        source: "content.main.title",
        maxLength: 96,
      },
      validation: (Rule) => Rule.required(),
    },
    {
      name: "illustration",
      title: "Illustration",
      type: "figure",
    },
    {
      name: "madeIn",
      title: "Made in ...",
      type: "string",
    },
    {
      name: "description",
      title: "Description",
      type: "text",
      rows: 3,
    },
    {
      name: "products",
      title: "Products",
      type: "array",
      of: [
        {
          type: "reference",
          to: [{ type: "product" }],
        },
      ],
    },
  ],
  preview: {
    select: {
      title: "title",
      media: "illustration",
    },
  },
};

hmm ok, I removed your custom types and refs. The schema seems ok.

export default {
  name: "collection",
  title: "Product Collection",
  type: "document",
  fields: [
    {
      name: "title",
      title: "Title",
      type: "string",
    },
    {
      name: "slug",
      title: "Slug",
      type: "slug",
      options: {
        // source: "content.main.title",
        source: "title",
        maxLength: 96,
      },
      validation: (Rule) => Rule.required(),
    },
    // {
    //   name: "illustration",
    //   title: "Illustration",
    //   type: "figure",
    // },
    {
      name: "madeIn",
      title: "Made in ...",
      type: "string",
    },
    {
      name: "description",
      title: "Description",
      type: "text",
      rows: 3,
    },
  //   {
  //     name: "products",
  //     title: "Products",
  //     type: "array",
  //     of: [
  //       {
  //         type: "reference",
  //         to: [{ type: "product" }],
  //       },
  //     ],
  //   },
  ],
  // preview: {
  //   select: {
  //     title: "title",
  //     media: "illustration",
  //   },
  // },
}

Hmmm, I commented everything out except for the title & slug and still ran into the issue... I'll keep checking

user U

yeah... same issue 🤔

I still feel like a noob with structure builder. Good practice op!
this
should just list document titles for collection type docs under the parent…

S.listItem()
          .title("Collections")
          .schemaType("collection")
          .child(
            S.documentTypeList("collection")
              .title("Collections")
              .child((documentId) => S.document().documentId(documentId))
          )
          .icon(BsGrid),

I may suggest trying to isolate what part of the
structure builder is causing issues. Try removing the structure builder in a test branch. This should just render each doc type and then you can make sure that your references and custom objects/types all work as intended. Maybe someone else can see something in your structure -vs- schema that I’m not. I’m building something kinda similar too and will circle back if any 💡 go off.
remove the builder part from

./sanity.json

to test similar to this:

"parts": [
    {
      "name": "part:@sanity/base/schema",
      "path": "./schemas/schema.js"
    },
    // - {
    // -   "name": "part:@sanity/desk-tool/structure",
    // -   "path": "./deskStructure.js"
    // - }
  ]

Looks like a pretty complex structure too… I’d definitely try isolating that at a very high level first with your full typical schema. And if the error still happens with structure builder removed - you’d be certain it’s an issue with referenced documents or objects.

it may also be good to check if custom document actions are being used - this could be another break point that can cause a relatively generic error like this

along with all this, don’t forget typical node troubleshooting - deleting modules, possibly also deleting the lock file - rebuilding

user U

thanks for the note on the structure. I inherited this project and it seems some of the syntax might have been out of date. Refactored and all is back to normal! Thanks

omg awesome, I feel your pain with inheriting a thing. Maybe you can find some joy in making it better. It’s a genuinely fun platform.

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Get started for free Explore the demo

Stack Trace: TypeError: Cannot Read Properties of Undefined (Reading 'Name')

The Solution

Troubleshooting Steps

Why This Happens

Sanity – Build the way you think, not the way your CMS thinks

Was this answer helpful?