[SOLVED] Designer "Launch client jar Invalid" error on Ubuntu

[Sheila_Villegas]

hello, i'm new using Ignition

First i install the gateway , then designer and finally try to lauch one but I encounter this error

don't know what happend

I'm using ubuntu and java 17

thank for the help

[Matrix_Engineering]

Welcome,

What version of Ubuntu?

[Sheila_Villegas]

Ubuntu 23.04

[Matrix_Engineering]

@Sheila_Villegas

23.04

Not officially supported.

Try this workaround:

Designer and Persective Workstation Apps not running on Linux

Hello, I''m having issues in running the designer app on an Ubuntu 22.04.3 LTS x86_64 machine. I noticed someone had the same issue on Mint back in 2019, but the workarounds didn't work for me. I tried both .desktop and .sh files but none work. It opens a terminal for less than a second and then nothing happens! Has anyone been able to run the Designer or Perspective Workstation apps on the mentioned distro? Thank you!

[Sheila_Villegas]

OGM IT WORKS
i copy the files to /usr/share/applications/ and run gtk-launch designerlauncher.desktop and works!

Thank you so much :')

[Matrix_Engineering]

You can mark this topic as solved, if you so wish, glad you got sorted

[cbabb]

I need to add to this... I was receiving this error also but under different circumstances.. in my case, I had a ver 8.1.31 app up in AWS. On the local computers at the customer site, I had the 1.1.31 versions of the Design Launcher and Vision Client Launcher loaded up and had no problem getting into the applications.

We decided to upgrade Ignition to 8.1.36 a few weeks ago and after installing the 1.1.36 versions of the launchers, started getting the Launch Client Jar Invalid message. But only on the computers at my customers site. On my local dev computer, I had no problem running the 1.1.36 launchers.

Going back to the 1.1.31 version of the launchers on my customers computers allowed us to get in but with a message to upgrade when we tried to launch them.

After some time with IA tech support, we were not able to resolve the error. In the end, the solution was on our end to whitelist the customers computer IP's in their firewall to allow the cert check to be allowed through.

It feels like something was added;/changed/enforced in the client launchers somewhere between 1.1.31 and 1.1.36..

[pturmel]

The launcher's own java changed from java 11 to java 17. Probably related.

[JordanCClark]

A few people at my shop had to delete their cache, even after upgrding the launcher.

[cbabb]

Jordan, that's typically my 1st step when I get something like this but it didn't help. As soon as the customers IT guys whitelisted the IP's of the computers in their firewall, everything started worked properly.