Posted 30 January 2025, 3:21 am EST
Hi Diego,
Please post the Wijmo related queries on the Wijmo’s Forums portal, as queries posted on the wrong portal may remain unanswered. Here’s the Wijmo forum link for your reference - https://developer.mescius.com/forums/wijmo
We found the following thread from your account, where the same issue has been raised - https://developer.mescius.com/forums/wijmo/error-build-when-update-wijmo-to-5-20241-19
It seems you haven’t yet found the root cause of the issue. The error message you shared doesn’t include any wijmo package names in it, so it would be difficult to say if Wijmo controls have caused this issue. However, we are assuming that you have upgraded only the Wijmo packages to 5.20241.19 version after which the issue is encountered (if you have made any other package upgrades or any other changes in your project, please make sure that is not causing this issue). As you are using Angular 11, we assume that you are using Wijmo’s legacy packages as suggested by our team in the above thread to resolve the compatibility issues.
You can try the following approach to investigate the root cause of the issue on your end -
Try commenting out/ removing the Wijmo components code one by one for each Wijmo component you have used in your project.
If the issue is getting resolved with the above step, then you’ll able to find the exact component in your code that is causing the issue. Now you can try removing the eventHandler or properties assigned to this component one by one and see if there is any specific event or property that is causing this issue. There is a very high possibility that there have been a lot of internal updates in the Wijmo component code in the latest version, which could be causing the issue. You can also try replacing the component with a new component with a few basic properties that are needed.
Using the above approach, hopefully, you’ll be able to find something that could help us find the root cause of the issue. Please share your investigation with us so that we can have a better understanding of the issue and assist you accordingly.
If possible, please try to replicate the issue in a sample and share it with us.
Regards