Anyone seen this error "Cannot read property 'sti' of null" and know how to solve it?
After upgrading to 2019.3.6 two of our reports doesn't render at all in the viewer and only showing this error.
2019.3.6 Cannot read property 'sti' of null
-
- Posts: 80
- Joined: Thu Aug 18, 2016 7:29 am
Re: 2019.3.6 Cannot read property 'sti' of null
Hello,
Please send us these two problem report to support@stimulsoft.com. We will check them and let you know what can be a reason.
Thank you.
Please send us these two problem report to support@stimulsoft.com. We will check them and let you know what can be a reason.
Thank you.
-
- Posts: 80
- Joined: Thu Aug 18, 2016 7:29 am
Re: 2019.3.6 Cannot read property 'sti' of null
I have found a solution for this problem. I had to add an empty space as default value for this string variable below. Seems like the JS version of 2019.3.6 doens't like empty string as default value anymore.
-
- Posts: 6247
- Joined: Tue Mar 20, 2018 5:34 am
Re: 2019.3.6 Cannot read property 'sti' of null
Hello,
We couldn't reproduce the issue.
Please send us a sample report with test data that reproduces the issue for analysis.
Thank you.
We couldn't reproduce the issue.
Please send us a sample report with test data that reproduces the issue for analysis.
Thank you.
-
- Posts: 80
- Joined: Thu Aug 18, 2016 7:29 am
Re: 2019.3.6 Cannot read property 'sti' of null
Attached simple report.
With JS 2019.3.6 it show both in the viewer and in the console
With JS 2019.3.6 it show both in the viewer and in the console
The data sent to the report, most likely not needed at all since I'm not showing anything in report other than a textbox.Cannot read property 'sti' of null
Code: Select all
{"CustomValues":{},"CompanyName":"Førtitoåringen Dev","Deleted":false,"ID":1}
- Attachments
-
- sti-of-null.mrt
- (4.2 KiB) Downloaded 119 times
-
- Posts: 6247
- Joined: Tue Mar 20, 2018 5:34 am
Re: 2019.3.6 Cannot read property 'sti' of null
Hello,
The issue is fixed. The fix will be available in the next release build.
Thank you.
The issue is fixed. The fix will be available in the next release build.
Thank you.