I got this error message when the screen is refreshed in a reactive app
I looked into the service center -> monitoring -> Errors, and got the following information, but I had hard time to find the cause from the message. Anyone know how to use the message to identify the source of the error?
======================================================
Message Expecting a Text, found: [object Object]
Environment Information
eSpaceVer: Id=259730, PubId=0, CompiledWith=11.12.0.29969RequestUrl: https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/moduleservices/log?clientTimeInMillis=1632856567327 (Method: POST)AppDomain: /LM/W3SVC/1/ROOT/DORS-1015-132773265097210083FilePath: D:\OutSystems\Platform Server\running\DORS.665724940\ClientIp: 206.29.176.51Locale: en-USDateFormat: MM/dd/yyyyPID: 9088 ('w3wp', Started='9/25/2021 8:00:32 PM', Priv=11239Mb, Virt=2133420Mb)TID: 1423Thread Name:.NET: 4.0.30319.42000Client Runtime Packages: client-runtime-core= 3.9.2;client-runtime-view-framework-react= 1.11.2;client-runtime-widgets= 1.11.2;Client-Side Log
Stack
TypeError: Expecting a Text, found: [object Object]at Function.t.ensureValidText (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystems.js?oay51q5QPx9P8Xmw2HkooQ:6:16819)at Function.t.checkType (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystems.js?oay51q5QPx9P8Xmw2HkooQ:6:14981)at t.setBasicProperty (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystems.js?oay51q5QPx9P8Xmw2HkooQ:6:13223)at t.set [as widgetIdInLocal] (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystems.js?oay51q5QPx9P8Xmw2HkooQ:6:20415)at Controller.OutSystemsUIController.default.setMenuListeners$Action (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystemsUI.controller.js?KUGkv5kYfc84Omwhkj5+5A:3807:28)at Controller._onReady$Action (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/TMobileReactive_Theme.Common.Menu.mvc.js?BZ3jcI8qNtHnzKKk7vVwGA:299:32)at https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystems.js?oay51q5QPx9P8Xmw2HkooQ:16:12997at d (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystems.js?oay51q5QPx9P8Xmw2HkooQ:2:15918)at f (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystems.js?oay51q5QPx9P8Xmw2HkooQ:2:15664)at Object.p [as tryCatchFinally] (https://xxxxxxxxxxxxxxxxxxxxxxxxxxx/DORS/scripts/OutSystems.js?oay51q5QPx9P8Xmw2HkooQ:2:16165)
Final update of this issue: the outdated producer modules were re-published and I update the reference dependencies and re-published my modules. After that the error message did not pop up again.
Hello Larry,
Can you describe the use case flow that precedes the error message?
You are probably already aware of this but for what I can read from the error detail is the following: somewhere in your code you're passing the wrong data type argument for some function.
Best,
Frederico
The error message pop-up when the screen was loaded before any user inputs were made. The module has reference to other module. When I publish the module, I noticed the warning on runtime error. Not sure if the error was due to referenced module(s):
Hi Larry,
I guess there is a javascript call OnReady (or other events) and that may cause the error. OR a data action that has advanced SQL call...
Please check inputs of them again if has any.
Regards,
Khuong
I'll subscribe what @Khuong Truong said. From the way it looks, it seems that the error is due to some JS code or with an advanced SQL call, but not 100% sure.
As @Tim Timperman also said, this issue seems to be happen with those JS code/SQL call on the TMobileReactive_Theme.Common.Menu and likely in the OnReady event.
First thing to do is to update all references in all modules and publish them to make sure that the consumers are using the latest implementation of its producers. If the error persists, try to give a look on any JS code you wrote, or imported from a component if it's the case, then do the same with all the data queries using parameters as filters.
I would say the error must be related to some parameter value in JS/SQL/action on the TMobileReactive_Theme.Common.Menu.mvc.js.
It seemed the outdated dependency modules were the cause. After these modules were re-published by the owners, the problem was resolved. Thank you for the suggestion.
There is a lot of information in that error log. The best place to look is in the stack trace.
The issue seems to happen in TMobileReactive_Theme.Common.Menu and likely in the OnReady event. Do you have any custom code in there?
Yes. This is dependent module by other developer. I have contact the owner and they re=published the module and resolved the issue.