Error after upgrade from v3.5.4 to v3.6.0

[bram-abe]

Bug report

Describe the bug

After migrate from v3.5.4 to v.3.6.0 the page (admin UI) not showing anything, just white/plain page.
so I try to remove the custom admin folder, then the login page can appear but after the login process the admin UI page still not showing anything.

Steps to reproduce the behavior

1. changing version in dependencies.
2. remove the old build
3. run npm build
4. run npm develop

OR

1. changing version in dependencies.
2. remove the old build
3. remove the custom admin folder
4. run npm build
5. run npm develop

Expected behavior

It should run properly after changing version in dependencies file as usual.

Error console

Error: react-error-boundary requires either a fallback, fallbackRender, or FallbackComponent prop
    at t.n.render (main.c0b10731.chunk.js:1)
    at Fi (main.c0b10731.chunk.js:1)
    at Ii (main.c0b10731.chunk.js:1)
    at gl (main.c0b10731.chunk.js:1)
    at cs (main.c0b10731.chunk.js:1)
    at ls (main.c0b10731.chunk.js:1)
    at Xl (main.c0b10731.chunk.js:1)
    at main.c0b10731.chunk.js:1
    at t.unstable_runWithPriority (main.c0b10731.chunk.js:1)
    at Vo (main.c0b10731.chunk.js:1)
main.c0b10731.chunk.js:1 Here is some infos
main.c0b10731.chunk.js:1 

System

• Node.js version: 14.16.0 LTS
• NPM version: 6.14.12
• Strapi version: 3.6.0
• Database: postgres
• Operating system: windows 10

[Igal-Kleiner]

Did you try to execute npm run build --clean?

[TasosBak]

I came across a similar error regarding ErrorBoundary. I had a custom admin\src\containers\PluginDispatcher\index.js and in that file the change that the team made was to go from
import ErrorBoundary from '../ErrorBoundary'; to
import { ErrorBoundary } from 'react-error-boundary';

so I suggest you search where that import exists in your custom admin pages.

Here is where I found how it is supposed to be after the update
PluginDispatcher/index.js

[bram-abe]

@TasosBak

I was remove node_modules, package-lock.json, build folder, and run new install with 3.6.0 deps.
and then follow ur guide, now the page can show ADMIN UI but showing new error like below :

main.13157256.chunk.js:1 TypeError: Cannot read property 'collectionTypesRelatedPermissions' of undefined
    at t.selectCollectionTypePermissions (main.13157256.chunk.js:1)
    at main.13157256.chunk.js:1
    at main.13157256.chunk.js:1
    at l (main.13157256.chunk.js:1)
    at v (main.13157256.chunk.js:1)
    at Ka (main.13157256.chunk.js:1)
    at gl (main.13157256.chunk.js:1)
    at cs (main.13157256.chunk.js:1)
    at ls (main.13157256.chunk.js:1)
    at Xl (main.13157256.chunk.js:1)

[derrickmehaffy]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/update-to-3-6-0-from-3-5-4-breaks-admin/4480/1

[TasosBak]

@derrickmehaffy The previous message is probably automated because I posted it in the forum asking for help - not providing any solution

[bram-abe]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/update-to-3-6-0-from-3-5-4-breaks-admin/4480/1

not solved the problem, like I was stated in my previous message it will get you to a new error message.

[soupette]

It seems that you made some customisations to your app. You'll need to check the changes from v3.5 to v3.6 and apply them again with the new codebase.

[TasosBak]

Thank you very much! What is the best way to check for changes between 3.5.4 and 3.6.0?

[soupette]

If you did not fork the package and used the extensions system it will be a difficult.
From what I see you have 2 options:

1. Check the PR Features/i18n #10000
2. Check the corresponding new files in your application.

[TasosBak]

Well that's 617 commits... Is there a recommended way to check which files have been changed from admin/src?

[soupette]

Which file did you change?

[TasosBak]

That's the thing - I've changed multiple files inside admin\src\components and in admin\src\containers.

I find it hard to believe that doing heavy customizations in the admin has not been done before. So there must be a way to check the files that have been changed in the new releases so that we are able to solve the issues that will come up.