Error signing ra.vg is not a function

Hello, I am using webviewer 11.9.0. On this particular PDF, when I sign it gives me an error.

Do you know what is causing this or how I can debug it?

Uncaught (in promise) TypeError: ra.vg is not a function
    at webviewer-core.min.js:2847:51
    at Array.forEach (<anonymous>)
    at ha.Cya (webviewer-core.min.js:2847:4)
    at ha.<anonymous> (webviewer-core.min.js:2845:355)
    at e (webviewer-core.min.js:75:70)
    at Object.next (webviewer-core.min.js:73:332)
    at z (webviewer-core.min.js:73:95)
(anonymous) @   webviewer-core.min.js:2847
ha.Cya  @   webviewer-core.min.js:2847
(anonymous) @   webviewer-core.min.js:2845
e   @   webviewer-core.min.js:75
(anonymous) @   webviewer-core.min.js:73
z   @   webviewer-core.min.js:73
Promise.then        
ea  @   webviewer-core.min.js:73
(anonymous) @   webviewer-core.min.js:73
ia  @   webviewer-core.min.js:73
ha.r9   @   webviewer-core.min.js:2844
(anonymous) @   webviewer-core.min.js:2844
e   @   webviewer-core.min.js:75
(anonymous) @   webviewer-core.min.js:73
z   @   webviewer-core.min.js:73
Promise.then        
ea  @   webviewer-core.min.js:73
(anonymous) @   webviewer-core.min.js:73
ia  @   webviewer-core.min.js:73
ha.fwa  @   webviewer-core.min.js:2843
(anonymous) @   SignatureModal.js:109
(anonymous) @   SignatureModal.js:2
(anonymous) @   SignatureModal.js:2
ke  @   SignatureModal.js:2
r   @   SignatureModal.js:2
Promise.then        
ke  @   SignatureModal.js:2
r   @   SignatureModal.js:2
(anonymous) @   SignatureModal.js:2
(anonymous) @   SignatureModal.js:2
(anonymous) @   SignatureModal.js:96
(anonymous) @   SignatureModal.js:89
(anonymous) @   SignatureModal.js:2
(anonymous) @   SignatureModal.js:2
ke  @   SignatureModal.js:2
r   @   SignatureModal.js:2
(anonymous) @   SignatureModal.js:2
(anonymous) @   SignatureModal.js:2
(anonymous) @   SignatureModal.js:88
(anonymous) @   useFocusOnClose.js:9    

i9-page-one.pdf (334.0 KB)

Hello, I’m AiRon, an automated tech support bot :robot:
While you wait for one of our customer support representatives, I can help you with your question.


It seems you are encountering a TypeError related to a function not being recognized in the WebViewer’s core JavaScript file. This could be due to a few reasons, such as a missing or incorrect library version, an issue with the PDF file itself, or a problem with the signature implementation.

Some things you can try:

  • Ensure you are using the correct and latest version of WebViewer. Check for any updates or patches that might address this issue.

  • Verify that all necessary libraries and dependencies are correctly included and configured in your project.

  • Test with a different PDF file to determine if the issue is specific to the file you are using.

  • Review your signature implementation to ensure it follows the recommended practices and examples provided by Apryse.

  • Check the browser console for any additional error messages or warnings that might give more context.



Here are some resources that might help you:


Hopefully, this helps you solve your problem while you wait for a human to get back to you.

note: I am upgrading from 11.1.1 and the signing is working in that version.

Hi there,

Thank you for reporting this issue and providing the file. I was able to reproduce the issue you are seeing in the viewer.

I will add this to the backlog for the product team to review and prioritize.

In the meantime, could you please provide the following information?

  • The impact of this bug for your workflow
  • How you generated this signature widget?

Best regards,
Kevin

This is bug is preventing us from upgrading. We are still on 11.1.1 b/c bugs in previous versions have prevented us from upgrading. As a customer it is very frustrating that every minor version has new bugs that prevent us from upgrading.

The signature widget was generated on the Apryse demo website.

I will attach a copy of the PDF before we fill in section one. The error is still occurring in this version.
i9_page_one.pdf (286.4 KB)

I am also attaching a screen recording where the second signature is placed in the first signature.

I was able to figure out the issue. There is a text field under the signature that was causing the issue. I removed the text field and it works now.

1 Like

Hi there,

Glad you were able to resolve this issue,

We will close this one out on our end.

1 Like

I believe this is still an apryse bug, will it be fixed?

i have gone ahead and created a support ticket for this.

1 Like