In the most common scenario, a control can handle server-side exceptions. For example, the MVC Scheduler control renders an exception's message in its markup.
The MVC GridView control displays the exception's message in the "alert" window.
However, when the exception contains an empty message, a client-side "TypeError: resultObj is undefined" error is raised and a current callback request can't be completed.
In the attachment, you can find a sample project and a video which illustrates how to reproduce the issue.
Throwing an empty server-side exception results in raising a client-side "TypeError: resultObj is undefined" error
Answers approved by DevExpress Support
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
- v15.2.4Download Official Update
- v15.1.8Download Official Update
Hello Gavin,
When an intermediate build that contains a hotfix for this issue is prepared, the "Hotfix requested" link will be changed to "Download hotfix" and a corresponding notification will be sent to all the trackers of this thread.
I see that this ticket is not in your favorites. I suggest you click the "Add to Favorites" button on this ticket page to get notifications of any changes related to this ticket.
Correspondingly, once the mentioned build is prepared for download, you need to download it, install and update your application.
See also:
How to request a hotfix
I hope you will find this information helpful.
You are welcome, Gavin!
If everything goes according to plan, an intermediate build which contains a hotfix for this issue will be prepared within a couple of days.
We will update the status of this ticket once this build is prepared for downloading.