Hello,
I have a Java app that I have built and bundled using:
Java 17 Temurin x64
JPackage
Fully signed
I have tested the created dmg and it runs without issues on Ventura with an M1. I have a customer using an Intel-i7 with Monterey who cannot run the program - the installer works. The error is "You can't open the application XXX because this application is not supported on this Mac".
I am not using XCode. My build is using ANT.
Is there a log somewhere that will give me more information about the exact error? Is this expected behaviour? The JDK I'm using is the x64 version, which should work with Intel.
Thanks!
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I had a process for generating an app using JPackage that was working well in Catalina. The signing process worked and generated apps that could be downloaded from my website and run without problems.
When my users had Ventura they could install from the dmg, but running the app gave "can't be opened because Apple cannot check it for malicious software". This is the error I used to get on Catalina before signing.
I updated my development computer to Ventura in the hopes that building using that OS version would clean up the problem, but no such luck.
The app runs without problems when I run it from the build location. I just get the above error when the dmg is downloaded from the internet.
The setting to allow applications from trusted developers is correct on my system.
I'm using:
Java 17 (though Java 20 does behaves the same)
Xcode 14.3 is installed (jpackage uses it under the hood)
My signing certificate shows as "this certificate is valid" in the system keychain
using "codesign -vvv --deep --strict" on the dmg and app claims "satisfies its Designated Requirement" (though I don't know what that means and there's no other information given)
Attempting to run codesign to sign the app tells me "already signed"
The code I have is pure Java, but does use JavaFX
There are no warnings or errors from jpackage when building
I would really appreciate suggestions on why the signing doesn't appear to be working any longer.
Thank you!