404 Error When Using Custom Path for WebViewer `ui` and `core` Folders

[jsam]

WebViewer Version:

Do you have an issue with a specific file(s)? No
Can you reproduce using one of our samples or online demos?
Are you using the WebViewer server? No
Does the issue only happen on certain browsers? No
Is your issue related to a front-end framework?
Is your issue related to annotations? No

Please give a brief summary of your issue:
Assistance Required: 404 Error When Using Custom Path for WebViewer ui and core Folders

Please describe your issue and provide steps to reproduce it:
We are currently integrating the Apryse WebViewer into a React-based SharePoint Framework (SPFx) application. While configuring the path to point to our hosted webviewer/lib folder, we noticed that the WebViewer initializes but fails to load the ui and core modules, resulting in 404 errors in the browser console.

Details:

• Environment: SharePoint Online + SPFx + React
• WebViewer Version: 11.5.0 (@pdftron/webviewer)
• Local Configured Path: Modal Development\<ApplicationName>\public

Issue we occured that webviewer.min.js:1
GET Sign in to your account 404 (Not Found)
input in the application
useEffect(() => {
if (!viewerRef.current) return;

    WebViewer(
        {
            path: '/public/lib',
            initialDoc: 'https://$$$.sharepoint.com/sites/KSSRMSSite/EDMS Document Library/Regulatory Filings-9Jun20256122/Contracts or Agreements.pdf',
            licenseKey: '****',
            fullAPI: true,
        },
        viewerRef.current
    ).then((instance) => {
        const { UI } = instance;
        UI.enableElements(['digitalSignaturePanelButton']);
        UI.setActiveLeftPanel('signaturePanel');
        console.log('WebViewer initialized with Digital Signature Tool');
    });
}, []);

[system]

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

It seems like you’re encountering a 404 error due to incorrect paths for the ui and core modules when using a custom path for WebViewer. This is likely due to incorrect configuration of the path property or mismatched file locations on your server.

Some things you can try:

• Ensure that the path specified in the WebViewer configuration matches the actual directory structure on your server.


• Verify that the files index-wc.html and other required files are present in the specified path.


• Check your server setup to ensure it allows access to the ui and core directories.


• Use the browser’s network tools to inspect the failing requests and confirm if the paths are correct.


• Double-check that the path in your code (/public/lib) is correctly routing to the intended location on SharePoint.

Here are some resources that might help you:

• WebViewer Initial Setup - Guide on setting up WebViewer correctly, including path configuration.


• WebViewer Deployment - Details on deploying WebViewer and managing paths.


• Integrating WebViewer, SharePoint Online, and PowerApps - Useful for ensuring correct integration with SharePoint.


• WebViewer Server Configuration Options - Although you’re not using a server, this can provide insights into potential configuration issues.

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

[luke.dam]

Hello Sam,

Thank you for contacting WebViewer Forums.

If you are hosting the WebViewer assets in a separate endpoint, there are a few extra configurations outlined in this documentation here: Loading WebViewer from another domain | Apryse documentation

To get a better understanding of the error, please provide any screenshots of network errors from the console. Typically if WebViewer is unable to load, there will be request errors to either the Core or UI assets.

Regards,
Luke

[jsam]

Image 1 : Which we got the error in application view

Image 2 : Issue we got in console

Image 3 : Application folder structure
Kindly guide me that how to append the correct path for the document viewer and for your information locally we call the path for the document viewer not from sever

[luke.dam]

Hello Sam,

As stated previously, please provide any network errors from the browser’s developer tools to investigate further. I would like to see the URL requests and fetches of the WebViewer assets and any request errors to diagnose further. Thank you!

Regards,
Luke