How do I get around the issue of start.jnlp not being able to run on MacOS Sequoia 15.1.1

[raymondjiii]

I don't even see an option to get around this. Most apps you can say "Open with" or something - nothing here. I did the uninstall of Java, then the re-install as shown on the Eisy: User Guide page.j

 

I have never rebooted this thing...ever. How do I do that? Push button once, twice, hold? Nothing seems to work. UD Mobile cannot connect so that's when I tried the start.jnlp which will not run.

[raymondjiii]

I should add that I can ping it at 192.168.1.151

[raymondjiii]

Answered one of my questions: For MacOS Sequoia open a terminal window, cd to the directory where start.jnlp is and enter: javaws ./start.jnlp

That works but I sill cannot find my eisy. My cable modem shows the mac address at 192.168.1.151 and I can ping that address. I cannot ssh to it - connection refused.

[raymondjiii]

Here you go: On MacOS Sequoia, once you try to start start.jnlp it will fail. Open "System Settings" go to "Privacy & Security" and towards the bottom will be something about how start.jnlp tried to start do you want to allow it? Click Yes/Always.

I used to really love Macs. One time I had a decent high power Macbook Pro that I did not have to reboot for over a year! And this was while doing development work on it. No joke. But these were the days when Steve Jobs really cared about quality. Now every MacOS update is a bunch of absolutely useless sh*t that the hippsters can go on social media and say "LOOK AT ME!, Ain't I cool?" No, you're not. I'd take performance and stability ANY day over these horsesh*t UI "features" - Okay, enough about Macs. I realize that the general audience here is Pro Windows. I used to be that way but then in 2011 I changed....maybe it's time to change back!

Edited December 6 by raymondjiii

[raymondjiii]

Well, I wish I knew what the hell I did....pushing the button 10 times, 5 times, 2 times (not in that order just trying different things)  IoX Launcher found the Eisy once (after countless failures) but couldn't could not connect to it again, even though it was right there in the IoX list. So I deleted it from IoX, got it showing up in IoX again - did a restore which oddly was from a 5.8.3 firmware backup made back in June 2024 (I have not added any devices since before June 2024). Then, either before or right after the restore I see that I am now at 5.8.4. I think the only safe way to do a firmware update is through UD Mobile. IoX is very odd in the UI when you try to update firmware. It does not give you any status, and tells that you need a reboot - really? After 0.0001 seconds from claiming to "start" to do the firmware update it has to be rebooted?

What a mess. I was about to try the HDMI video and USB keyboard and mouse next (never tried that). I still cannot figure out how UD Mobile "lost" contact with this Eisy. UD Mobile must get into a state or save something about the Eisy and that after the hard reset, reboot, failure, whatever - it loses access even though everything goes through UD portal. I eventually got UD Mobile going with 2 Eisy's (1 was ending with a (1) I think). I got my favorites listed but there was a big red triangle at the top of UD Mobile anyway. I just did a synchronize on one device and trashed the other. Thank god, I had a lot of lights on outside that I didn't want the neighbors bitching about and I really didn't want to be out in the 20 degree weather fiddling around on the snow trying to turn off every damn outlet outside at 2am.

Even after a reboot, shouldn't the Eisy automatically show-up in UD Portal? UD-Portal was stating that it had not seen my device online since XX:XX:XX (a couple of hours before I was trying to resolve this).

Also, what does "holding" the Eisy button do, which turns the power button red - I assume that turns it off??? Okay, but if you push it again it immediately goes blue but I guess it's not really "online" for a couple of minutes or so. There is a bit of documentation that said to not try to connect to it until after 5 minutes from starting and if you try to connect before the 5 minutes then bad things will happen (I'm paraphrasing here). It would be nice if maybe the indicator light went red (off) to yellow (starting) to blue (ready) - or something like that so you know exactly when things are online and ready to go. I find it odd that you could screw things up by "trying to connect to the Eisy too early" - at least that's how I read it. I would think/hope that the connection would just fail if the device was not ready and there would be no long term effects to the device, IoX or UD Mobile configs.

Well, hopefully "at least" another couple of years before another "connection" problem.

Edited December 6 by raymondjiii

[paulbates]

The eisy in unique in that there are different functions associated with pressing the power button X times... I don't have the link right now

My suggestion is for you to submit a ticket

[macjeff]

I wrote up about this on the wiki, but 15.1.1 (And the 15.2 betas have a bug)

Just last night, I reported this to Apple, and we have a workaround that worked for me. It's ANY program that uses a device on a local network, even a scanner or pg3x. I know you probably are aware of a lot of the instructions below. I am going to give you step-by-step instructions so others can do this also.

1. Go to system settings under Apple menu

2. go to Privacy and Security

3. Go to LOCAL NETWORK (only in Sequoia)

now, here is where the workaround starts

4. if you have something in there, turn it off.  If you don't we may have to find a different solution

5. Reboot the computer

6. Turn what you turned off in privacy back on

7. Run all the programs that might use the Internet, like start.jnlp, your scanner, all your browsers going to IP, any LAN scanners, FTP programs, and don't forget the IOX launcher. They should ask you to ALLOW the connection. Make sure you click Allow on each one. 

8. Check the Privacy and Security of the local network.  They should add it there.

 

The bug is that when you reboot, the file gets locked, but the procedure above unlocks it. Unfortunately, there is no way to manually edit or delete the preferences, so until Apple fixaes the bug, every reboot will lock it.

I have sent an email to UD saying if you put in a ticket, I can work with you directly since I also had this issue and got the workaround to work.

[raymondjiii]

Okay thanks I'll try that. Currently I have 10 items there including "IoX Launcher". I was just going to create a shortcut to run "javaws start.jnlp" - that avoids all of this (at least it did last night). I had a ticket open with UD but that was for the weirdness I was experiencing with the Eisy - which I think is also resolved...I hope.

I just installed Sequoia last night. I was waiting until December when I knew that if something would be altered (like my other programs) I would have time to resolve but I wasn't expecting this problem. I doubt apple is going to fix this anytime soon. I have a large list of UI bugs in MacOS Apple Music (been there since day 1 when it was "iTunes") not a single one was fixed. These are not common things that the average person would do but I spend a large amount of time using Music but you'd think Apple's QA department would have caught some of these.

Thanks for your reply!

[macjeff]

I encourage you to report this to feedback.apple.com.  They are telling me this is not an urgent bug but it is.  When you cant use a device on your network thats URGENT to me.

When you get START to run you will see the JAWS in the list,  See my screenshot.  Thats just some of mine. 

 

Another thing that makes me mad is when you go from 15.1.1 to 15.2 (in release candidate now so probably next week) it will delete most of the items and you have to re-add them.  The same procedure worked for me.

Oh...one more thing.  After installing 15.2 when it comes out you can add all you want to add before the first reboot after update.  (it reboots for update and that does not count).  Once you reboot manually the issue comes back.

 

 

 

[bigDvette]

You can also add it manually.  Just add the device by typing https://IP_ADDRESS:8080/desc   in the window that pops up. It adds it locally.  If it ever finds it on the network you will see it as eisy.local.   I have 1 Mac I can't get to find it automatically. I know it is the network setting to allow local access.  There is process to reset all of that I just haven't messed with yet.

 

[raymondjiii]

11 minutes ago, bigDvette said:

You can also add it manually.  Just add the device by typing https://IP_ADDRESS:8080/desc   in the window that pops up. It adds it locally.  If it ever finds it on the network you will see it as eisy.local.   I have 1 Mac I can't get to find it automatically. I know it is the network setting to allow local access.  There is process to reset all of that I just haven't messed with yet.

 

It wasn't adding it. I knew exactly what the IP address as I could see it's MAC address in the router (MAC address is on the bottom sticker) - so I was 100% positive I had the right IP address. I tried http:8080 and https:8443. As I said after "pushing buttons"...for a while...it was able to show and then I had to restore it from a backup.

[macjeff]

12 minutes ago, raymondjiii said:

It wasn't adding it. I knew exactly what the IP address as I could see it's MAC address in the router (MAC address is on the bottom sticker) - so I was 100% positive I had the right IP address. I tried http:8080 and https:8443. As I said after "pushing buttons"...for a while...it was able to show and then I had to restore it from a backup.

Thats the bug in 15.1.1 and 15.2 (coming very soon).   The work around I sent should work,  You will see the _JAVAWS in the local network if fixed.

Realized I forgot screenshot in previous post.  Here it is

 

[raymondjiii]

8 minutes ago, macjeff said:

Thats the bug in 15.1.1 and 15.2 (coming very soon).   The work around I sent should work,  You will see the _JAVAWS in the local network if fixed.

Realized I forgot screenshot in previous post.  Here it is

 

Also, before this in "Privacy & Security" down near the bottom you will see a little box saying that start.jnlp was prevented from starting (because it's not signed by a developer or whatever) so you have to enable that first - it's hard to see and you would not think to even look there - at least I didn't. I was trying to do "Open With..." etc and that's when I found that at cmd prompt you could run: javaws ./start.jnllp and that did not have any issues. But I do see javaws in the list now (the same list you are showing above.) Every upgrade, I think more is broken than added. Maybe it will be nice that I can access the iphone screen on the Mac - time will tell if that's useful for me.

[macjeff]

2 hours ago, raymondjiii said:

Also, before this in "Privacy & Security" down near the bottom you will see a little box saying that start.jnlp was prevented from starting (because it's not signed by a developer or whatever) so you have to enable that first - it's hard to see and you would not think to even look there - at least I didn't. I was trying to do "Open With..." etc and that's when I found that at cmd prompt you could run: javaws ./start.jnllp and that did not have any issues. But I do see javaws in the list now (the same list you are showing above.) Every upgrade, I think more is broken than added. Maybe it will be nice that I can access the iphone screen on the Mac - time will tell if that's useful for me.

Thats actually a new feature which I hate also.  Those of us who have used mac for a while remember where you could allow all apps to open and then as you stated it was with open with.  Now you have to go to privacy.  Such a pain.  I thought you were trying to get it into LOCAL NETWORK also under privacy.  My fix will fix that but you figured out how to allow it.  I never saw that with start, probably because I had it allowed for a while.

[raymondjiii]

No, it's not there when you right click. "Open With" is still there but nothing in the list worked for start.jnlp. I just searched for how to get around the restriction on running a jnlp file on Sequoia and .... "AI" found running it on the command line.