I'm trying to open the 8.1 samplequickstart project in the designer and not seeing the perspective tab in the sidebar
Here's the logs:
java.lang.NoSuchMethodError: 'java.util.Optional com.inductiveautomation.ignition.client.util.JxBrowserUtil.getOrCreateEngine(com.inductiveautomation.ignition.client.launch.LaunchContext, com.teamdev.jxbrowser.engine.RenderingMode, java.lang.String, java.lang.String)'
at com.inductiveautomation.perspective.designer.DesignerHook.startup(DesignerHook.java:227)
at com.inductiveautomation.ignition.designer.IgnitionDesigner$LoadedModule.startup(IgnitionDesigner.java:2003)
at com.inductiveautomation.ignition.designer.IgnitionDesigner.startupModule(IgnitionDesigner.java:1200)
at com.inductiveautomation.ignition.designer.IgnitionDesigner.loadProject(IgnitionDesigner.java:1003)
at com.inductiveautomation.ignition.designer.IgnitionDesigner$StartupProjectDialogHandler.lambda$new$2(IgnitionDesigner.java:2047)
at java.base/java.lang.Thread.run(Unknown Source)
that prooooobably shouldn't fail silently if it fails
You've upgraded incorrectly somehow; NoSuchMethodError
indicates a mismatch between the expected JxBrowser API we've compiled against and the actual dependency jar you've gotten.
Do your Perspective module and base Ignition build dates align?
How do I check those?
I just tried using the 'download designer launcher' from my installed ignition 8.3 build and observed the same issue
First, check the modules page (/app/platform/system/modules
) and the build version there - make sure it lines up with the version from whatever installer you last used.
Then to verify JxBrowser you need to check the filesystem directly. In $installDirectory/lib/opt/jxbrowser
there'll be a bunch of versioned jars per platform, which should all be 8.5.0.
All my modules look like they have the same version, (b2025041016), and all my JARs are 8.5.0
I can upgrade this evening and let y'all know if the issue persists
Upgrading running the ignition installer didn't fix it, but manually installing the modl file did. Weird
Might be an issue with the version detection logic in 8.3, since they're both "dev" versions, so maybe the installer didn't properly nuke/replace the old version. For now I'll chalk it up to that.
makes sense -- maybe note that in the deployables thread?