We recently upgraded a site from Maple (Tutor V13) to the latest Redwood (Tutor V18). This error occurs if I click “Account” after logged in: “An unexpected error occurred. Please click the button below to refresh the page.”. Refreshing the page doesn’t work.
When I looked at the browser console, the account info pulled by ajax /api/user/v1/accounts/myuname worked fine. it appears it is caused by a JS error in the file
webpack://edx/frontend-app-account/node_modules/react-dom/cjs/react-dom.production.min.js 216:199
“Error: Minified React error #130;”
Not sure what is causing it and how to fix it. Please help!!
BTW, the site was initially launched from AWS Tutor AMI a few years ago.
Similar issue. Nothing evident in the logs, seems to be an issue with some JS. I’m currently too new to upload images, however it’s the same issue as @jennyq
Environment is self-hosted Tutor on AWS, but I’m using my own installation script.
Interestingly, I’d been honing my script and so over the past few weeks tearing down and rebuilding our Tutor configuration from scratch (SSO, additional XBlocks). Everything was working well until recently when I started re-deploying the production version, leveraging the latest tutor.
Originally I thought it was something related to rebuilding the OpenEdx docker image with some additional xblock plugins. However, on a recent run, I limited the installation to stock 18.1.2 and still had the same issue with some strange 500 / unexpected errors—the accounts page being the quickest and most consistent to reproduce (every time).
Then, in an effort to debug further, I started working my way backwards, installing previous versions and the issue listed here went away when I configured Tutor around a core version of 17.0.6.
So it seems everything > 18.0 is affected, including 18.1.3 released today. I tried each release:
18.1.3 (error)
18.1.2 (error)
18.1.1 (error)
18.1.0 (error)
18.0.0 (error)
In all cases this was a fresh, non-upgraded install so it likely has little to do with an upgrade and something to do with the JS assets.
I tried this on multiple browsers as well: FF, Chrome, Safari. Even different networks in case network filtering was the cause. No changes sadly.
I hope this helps the team get to the bottom of it. Thanks for all you do!
@Danh_Vo I think the most likely way forward for most of us, at this point, is probably to use the 17.x series, and in the meantime we file a bug with the Tutor maintainers.
That’s what I’ve done. I back ported our changes to 17.0.6 and put that into production.
Before we file a bug someone could also check if the development version of Tutor, which likely wouldn’t have the minified / processed JS assets, has the same issues. That would help narrow down the issue: is it a web-assets-processing-pipeline issue or an issue with the code itself?
I am expecting that the issue you’re encountering is due to an incompatibility between the account-mfe and the custom indigo-footer. We are currently working on resolving this issue. In the meantime, could you please switch to “Tutor Indigo v18.0.0” until the fix is implemented? Please feel free to share if you face the issue with “Tutor Indigo v18.0.0”. It will help me in investigating in detail.
We sincerely appreciate your patience and understanding.