Can you reproduce using one of our samples or online demos? Yes, reproducible by using the WebViewer UI 8.1.0 source code with Core 8.3.3.
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? No (Custom UI implementation)
Is your issue related to annotations? No
Please give a brief summary of your issue: WebViewer promise does not resolve when using Core 8.3.3 with UI 8.1.0 (Loader spins infinitely)
Please describe your issue and provide steps to reproduce it: I am upgrading my WebViewer Core from version 8.1.0 to 8.3.3 while keeping my UI at version 8.1.0 (which is a custom UI based on the webviewer-ui GitHub repository).
When running Core 8.3.3 with UI 8.1.0, the viewer fails to initialize properly. The top header is visible, but the loading spinner remains indefinitely. Debugging shows that the WebViewer(...) promise never resolves or rejects.
I have confirmed that this is a version-specific compatibility issue:
It works perfectly when both Core and UI are on 8.1.0.
It works when Core is downgraded to 8.3.2 with the 8.1.0 UI.
The issue is reproducible even when using the standard/unmodified 8.1.0 UI code with the 8.3.3 Core.
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 experiencing a compatibility issue between different versions of the WebViewer Core and UI. When the WebViewer promise doesn’t resolve, it usually indicates a problem with loading resources or initializing components, which can often be traced back to version mismatches or missing dependencies.
Some things you can try:
Ensure that all required resources for the WebViewer Core and UI are correctly loaded and accessible.
Check for any console errors or network issues that might provide further insight into what might be failing during initialization.
Consider aligning the versions of WebViewer Core and UI to ensure compatibility, as mismatches can lead to unresolved promises and other issues.
Verify that your custom UI implementation does not have any dependencies or scripts that are incompatible with the newer Core version.
Review any changes or updates in the newer version of the Core that might impact your configuration or initialization logic.
WebViewer Server API Wrapper: Although not directly related to your issue, this resource provides insights into the server-side API that might help in debugging similar issues.
Integrate WebViewer into Nuxt 2: This sample can offer ideas on how to integrate and troubleshoot WebViewer in different environments.
We recommend that you upgrade both the Core and UI to the same versions. If you are upgrading to Core 8.3.3, you should also use UI 8.3.3 as mismatched versions is known to cause compatibility or initialization issues.
What we want to do is use our same custom UI with latest versions of Core. Based on your recommendation of upgrading both Core and UI to newer same versions, this would mean that we will have to rewrite our custom UI logic in the latest version of UI. Is there any way to avoid that?
There is currently no workaround to rewriting the custom UI for a new version however, porting over your changes should be relatively easy if there are no major changes between the base UI code. For more information on custom UI, please see our documentation here: Advanced UI Customization | Apryse documentation
I would also recommend looking into upgrading to the latest version 11.10 if you have a chance. Our legacy versions will be deprecated in the near future. More information here: Legacy UI for WebViewer | Apryse documentation
