Hi,
With the recent version 20.2.0.43 the PDFViewer component when opening a document with the javascript "load" function and passing it the content in base64 opens it correctly but it shows the following message and I understand that it should not show it if it works correctly.
The web service works fine and the document opens correctly.
Regards.
Hi Pere,
We were unable to reproduce the reported issue with the provided details. We have shared the sample in which we tried to reproduce the issue in the below link.
https://stackblitz.com/edit/vxjdjb-dwknt2?file=index.js,index.html
Kindly try this and revert to us with modified sample, code snippet, replication procedure and more details about the reported issue if you have any concerns. Moreover, if you can share us the screenshot of the response tab, it will be good to know what caused the error. Kindly share the requested details to analyze further to resolve the issue.
Regards,
Arun Kumar
I am trying to reproduce the error but I think it is a very specific case of the CMS (Drupal) I am using.
I have a form where in the first step I upload a file and in the next step the PDFViewer opens the uploaded file. It only shows the error when a file is uploaded before, if no file is uploaded (I open a previously uploaded file) it does not show error. In both cases the file is displayed correctly in the PDFViewer.
I don't understand why it fails, because in both cases the PDFViewer DocumentPath is assigned the content of the file in base64 (a string). Maybe when the file is uploaded with the Drupal CMS component it uses a streamer that then causes the PDFViewer to fail even though the file is actually displayed correctly.
As a workaround I am setting the showNotificationDialog variable to false so that it does not display the web service error message.
I will try to find out better why this happens and if I find it I will write you again.
Thank you very much.
Hi Pere,
Thank you for Contacting Syncfusion support
Kindly check the reported issue with our sample provided earlier. If the document loads properly in our sample, may be the issue occurs due to the usage of CMD (Drupal). So Kindly check with that and try to provide us a simple sample that reproduces the issue for further validation
Regard,
Arun kumar