You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @vsquared! Yes, @SableRaf and I saw this recently as well and as far as I understand is limited to arm based Macs. We traced the issue to the accidental upgrade from JDK 17.0.8 to JDK 17.0.14. This will also be fixed by either upgrading the JDK past version 17 or with this approach which should undo the accidental upgrade.
Thank you and SableRaf for all of your work on the Processing editor; I like version 4.4.1 otherwise; it has a nice solid feel. I checked my java --version in Terminal and have the following on my macos silicon system (M2):
You may mean to upgrade Processing's JDK? I think I remember reading that it has its own JDK? I have to plead ignorance on how to implement either option 1 or option 2. Another option is just to wait on your next version since you are now putting them out more frequently. I have an older version on my system that I modified and re-compiled to run JavaFX that I can use in the meantime.
Ah yeah sorry I shared some paths for me to take going forward to solve this issue. I think right now there is not anything you can fix for 4.4.1 to make it work on a Mac. Now that I think about it, you could try downloading the 17.0.8 jdk from here or here and replacing the contents of Processing.app/Contents/app/resources/jdk-17.0.14+7/ with the contents of the downloaded version.
I'll try and see if I can pull the fix in my runner branch forward to 4.4.3 so you'd have a working version next month.
First link didn't work and second link seemed to go to wrong version (I could have missed it), so I downloaded jdk-17.0.8 from here: https://www.oracle.com/java/technologies/javase/jdk17-archive-downloads.html and then made the substitution in the app bundle and it worked! I can now run JavaFX with Processing 4.4.1. Thank you so much for taking the time to explain how to fix it. I was afraid the Apple gatekeeper would catch me, but he didn't.
Activity
Stefterv commentedon Apr 18, 2025
Hey @vsquared! Yes, @SableRaf and I saw this recently as well and as far as I understand is limited to arm based Macs. We traced the issue to the accidental upgrade from JDK 17.0.8 to JDK 17.0.14. This will also be fixed by either upgrading the JDK past version 17 or with this approach which should undo the accidental upgrade.
vsquared commentedon Apr 18, 2025
Thank you and SableRaf for all of your work on the Processing editor; I like version 4.4.1 otherwise; it has a nice solid feel. I checked my java --version in Terminal and have the following on my macos silicon system (M2):
You may mean to upgrade Processing's JDK? I think I remember reading that it has its own JDK? I have to plead ignorance on how to implement either option 1 or option 2. Another option is just to wait on your next version since you are now putting them out more frequently. I have an older version on my system that I modified and re-compiled to run JavaFX that I can use in the meantime.
Stefterv commentedon Apr 18, 2025
Ah yeah sorry I shared some paths for me to take going forward to solve this issue.
I think right now there is not anything you can fix for 4.4.1 to make it work on a Mac.Now that I think about it, you could try downloading the 17.0.8 jdk from here or here and replacing the contents ofProcessing.app/Contents/app/resources/jdk-17.0.14+7/with the contents of the downloaded version.I'll try and see if I can pull the fix in my
runnerbranch forward to 4.4.3 so you'd have a working version next month.Thank you for the nice words! 💙
vsquared commentedon Apr 19, 2025
First link didn't work and second link seemed to go to wrong version (I could have missed it), so I downloaded jdk-17.0.8 from here: https://www.oracle.com/java/technologies/javase/jdk17-archive-downloads.html and then made the substitution in the app bundle and it worked! I can now run JavaFX with Processing 4.4.1. Thank you so much for taking the time to explain how to fix it. I was afraid the Apple gatekeeper would catch me, but he didn't.