MyController V2.0 Error: Minified React error #31
I installed MyController V2.0 docker version on a nanopi zero.
All the prerequisistes are satisfied:
- Docker installation
- InfluxDB configured and container started
- Mosquitto configured and container started
- Natsio configured and container started
- MyController configured and container started
Looking at MyController logs:
docker logs --follow mycontroller
I can't find any error, but trying to access the homepage I receive the following error message:
Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args=object%20with%20keys%20%7Bt%2C%20input%2C%20schemaCheck%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings. Component Stack Details: at strong at div at c (http://192.168.8.194:8080/static/js/2.84cd2603.chunk.js:2:2137549) at a (http://192.168.8.194:8080/static/js/main.a9d44749.chunk.js:1:1518) at a (http://192.168.8.194:8080/static/js/main.a9d44749.chunk.js:1:367371) at r (http://192.168.8.194:8080/static/js/2.84cd2603.chunk.js:2:2053282) at C (http://192.168.8.194:8080/static/js/2.84cd2603.chunk.js:2:38004) at Suspense at t (http://192.168.8.194:8080/static/js/2.84cd2603.chunk.js:2:1132350) at u (http://192.168.8.194:8080/static/js/2.84cd2603.chunk.js:2:35902) at sj at t (http://192.168.8.194:8080/static/js/2.84cd2603.chunk.js:2:169455) at t (http://192.168.8.194:8080/static/js/2.84cd2603.chunk.js:2:848785)
Is there something that I missed? Can someone help me on this?
Hi @giuseppez thanks to report this issue. Seems I broke something. I am looking into it.
till then you can use the following image
I have created an GitHub issue to track this
@giuseppez the issue has been fixed in https://github.com/mycontroller-org/console-web/commit/a6968fcecedcc598f684d7d3102d7f5be42aa8c2
container images are updated, you can take the most recent build
@jkandasa thank you for the prompt answer. As soon as I will have a little bit of time I will try your fix and let you know
@jkandasa now is fine. Thank you very much
@giuseppez thanks to confirm the fix status!