when i open file my pdf have some comments in this file. but i see have error Value cannot be null. (Parameter 'data') when load page. same issue when open this file on link demo of syncfusion https://ej2.syncfusion.com/aspnetcore/PdfViewer/Default#/fluent
I attached my pdf file in attachment bellow. please check it
We can reproduce the reported issue in our online demo, and it is fixed in our latest weekly release. Please upgrade to the latest version(V20.3.52) to resolve the reported issue. We have shared the simple sample in our latest version.
Clint-side sample: https://stackblitz.com/edit/react-h3gppa?file=index.js,index.html
Server-side sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/ControllerSampleCore1031458474.zip
Steps to run the sample:
If still facing the issue, modify the shared sample and revert to us with more details.
this issue still ocur with source server-side sample above
https://www.syncfusion.com/downloads/support/directtrac/general/ze/ControllerSampleCore1031458474.zip
, please check my source front end vs backend in attachment
+ FE: npm i + npm start
+ BE : run vs 2022 + net 6.0
We were able to reproduce the reported issue “Render Annotation Comments returns an error while loading the given document in .Net6.0” and suspect this to be a defect. We will validate it and update further details.
We have confirmed the issue "Script error occurred while loading the particular document in .NET6.0 framework" and logged it as a defect. The fix for the issue will be available in our upcoming weekly NuGet release on November 23, 2022. You can track the status of the issue through the following link.
Feedback Link: script error occurred while loading the particular document in .NET6.0 framework | Issue Feedback
Disclaimer: "Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization."
We have fixed the reported issue "Script error occurred while loading the particular document in .NET6.0 framework" and the fix for the reported issue was included in our latest weekly release v20.3.0.58. Kindly upgrade to that version to get the issue resolved.
Packages:
CDN Links: