Migrating from v3 to v4

Questions and Answers
1
System Information
  • *Strapi Version *:
  • **Operating SystemMac OS Intel:
  • **DatabasePostgress:
  • **Node Version18.16.0:
  • **NPM Version9.5.1:
  • **Yarn Version1.22.9:

Trying to migrate from strapi v3 to strapi v4, but getting stuck with bellow error.

yarn run v1.22.19
$ auto/develop.bash
[2023-04-25 17:10:41.681] debug: :no_entry: Server wasn’t able to start properly.
[2023-04-25 17:10:41.683] error: Could not find field size for type group
Error: Could not find field size for type group
at getFieldSize (/Users/sachinshetty/sh-yc-advisory-cms/node_modules/@strapi/plugin-content-manager/server/services/field-sizes.js:58:13)
at getDefaultFieldSize (/Users/sachinshetty/sh-yc-advisory-cms/node_modules/@strapi/plugin-content-manager/server/services/utils/configuration/layouts.js:25:10)
at appendToEditLayout (/Users/sachinshetty/sh-yc-advisory-cms/node_modules/@strapi/plugin-content-manager/server/services/utils/configuration/layouts.js:130:27)
at createDefaultEditLayout (/Users/sachinshetty/sh-yc-advisory-cms/node_modules/@strapi/plugin-content-manager/server/services/utils/configuration/layouts.js:47:10)
at createDefaultLayouts (/Users/sachinshetty/sh-yc-advisory-cms/node_modules/@strapi/plugin-content-manager/server/services/utils/configuration/layouts.js:31:11)
at createDefaultConfiguration (/Users/sachinshetty/sh-yc-advisory-cms/node_modules/@strapi/plugin-content-manager/server/services/utils/configuration/index.js:26:20)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async generateNewConfiguration (/Users/sachinshetty/sh-yc-advisory-cms/node_modules/@strapi/plugin-content-manager/server/services/configuration.js:53:36)
at async Promise.all (index 15)
at async Object.syncConfigurations (/Users/sachinshetty/sh-yc-advisory-cms/node_modules/@strapi/plugin-content-manager/server/services/configuration.js:67:5)
error Command failed with exit code 1.
info Visit yarn run | Yarn for documentation about this command.

2

I am also getting the same error message