Unable to add a Component to a Dynamic Zone after 4.15.1 upgrade

[dennism501]

Bug report

Required System information

• Node.js version: 20.9.0
• NPM version: 10.1.0
• Strapi version: 4.15.1
• Database: SQLite
• Operating system: Mac OS
• Is your project Javascript or Typescript: JS

Describe the bug

After upgrading to 4.15.0 and 4.15.1 as well, I am unable to add a component to a Dynamic zone. Whenever you try to add a component to a DZ, the page breaks and you can not procede

Steps to reproduce the behavior

1. Update package.json to Strapi 4.15.*
2. delete node_modules, yarn.lock, .cache
3. Run yarn && yarn build && yarn develop
4. Go to any content type with a Dynamic zone in the Content Type Builder
5. Click on add component button
6. See error

Expected behavior

Being able to add a component to a Dynamic Zone in the content type builder

Screenshots

I created this loom video to show the steps of recreation.

Code snippets

If applicable, add code samples to help explain your problem.

Additional context

Add any other context about the problem here.

[dennism501]

Escalation with TID: 5147

[Ceyapps]

i'm having the same issue

[dgrebb]

Also impacting a big project for me.

I've tried downgrading back to 4.14.2, which also has this issue, as well as each patch/minor version up to and including 4.15.2, which is a no-go as --legacy-peer-deps requires changes across CI (and the issue persists).

I get a different error, but it's in the same reproducible step @dennism501 shared. Clicking the "Add Component" button throws:

Uncaught TypeError: r is undefined
    xa http://localhost:1337/admin/content-type-builder.2d053d33.chunk.js:149

Database corruption? Making manual changes to the schema files has been OK, but I'm blocked on a large, dynamic-component heavy feature.

[dgrebb]

I had an empty 4.14.0 install laying around — for all intents and purposes fresh and clean.

Copied over api and components, fired it up, and everything is working, including "Add Component", through to the publish of content.

I'll take a deeper look into whether this might be directly related to using postgres, which is in use in the envs where this error is popping up (for me).

@dennism501 @Ceyapps what DBs are you using?

[remidej]

@dgrebb I have the bug despite using sqlite 😕