App Startup Issues after Upgrade to MacOS Sequoia

[Lmsshepard]

Java8 Springboot Maven built App (IntelliJ with Fvarrui javapackager plugin) will not start now that I have upgraded to MacOS Sequoia. Prior to upgrading to Sequoia I did not bother to code sign app or get it notarized. Now, having upgraded to Sequoia, code signing and notarization by Apple is required. I have added the appropriate setting to the pom.xml file within the javapackager plugin section to code sign and notarize. Although there are a couple errors, the App gets submitted to Apple, notarized and stapled fine. However, when I click the App, it fails to launch. I have read issue#448 and tried the various suggestions, but none work.

When I do NOT specify "macStartup" or a custom launcher (i.e. native ARM64 or Universal ARM64), I am able to click on the universalJavaApplicationStub to launch the App. Any other launcher will not work when either clicking the App itself to launch or one of the other script (i.e. native ARM64 or Universal ARM64). Another thing to note is the when using the default - universalJavaApplicationStub the build info steps indicate that the universalJavaApplicationStub replaced the code sign without error. When trying either of the other 2, the replace code sign fails.

Lastly, as mentioned above when using the default exe script (universalJavaApplicationStub) the code sign replace works fine, however, the App code sign replace fails. Regardless of this failure, the app builds and is submitted for Notarization and Stapling and both pass.

[Lmsshepard]

I intended this to be addressed by Fvarrui who authored the javapackager. I am attaching pertinent files.

SysConsoleOutput.docx
Launch Error.docx
Build Output.docx
Info.plist.txt
pom.xml.txt

[Lmsshepard]

[Lmsshepard]

Adding additional information / template:

Short description of the issue/suggestion:
After upgrading to MacOS Sequoia and being required to code sign and notarize my app, cannot launch app even though code sign and notarization pass

Please tell us about your environment:
MacBookPro
Chip Apple M2 Max
32 GB
JavaPackager version: 1.7.6
OS version: macOS Sequoia 15.0.1
JDK version: jdk-1.8
Build tool: Maven

Steps to reproduce the issue:
DMG Maven Build of Spring Boot /Java (version 8) application with JavaPackager using default universalJavaApplicationStub. Code signing and Notarization / Stapling PASS and App installs in Application folder, however cannot launch App. Although code sign and notarization pass, it is interesting that in the build output, prior to it submitting to Apple, there is a error stating that the App code sign could not be replaced.

What is the expected behavior?
App launches when double clicking the application icon

What have you tried to resolve / workaround the issue?

1. customLauncher = universalJavaApplicationStub.arm64 (macStartup = UNIVERSAL or macStartup = ARM64). Build output shows error with universalJavaApplicationStub.arm64 code sign replacement. However App builds and passes code sign and notarization/staling. Still cannot launch App.
2. customLauncher = nativeJavaApplicationStub.arm64Activity (with macStartup = ARM64). Build output shows error with universalJavaApplicationStub.arm64 code sign replacement. However App builds and passes code sign and notarization/staling. Still cannot launch App.
3. Install via package rather than DMG - same result
4. Can launch App by opening up the app Content/MacOS folder and clicking directly on the universalJavaApplicationStub. Note requires that you allow it to run within the Security and Privacy settings.

Attachments:
See previous comments where I have attached the following:

1. pom.xml
2. info.plist
3. maven App build debug output
4. System Console output (after trying to launch app)

[fvarrui]

Hi @Lmsshepard!
I'm very sorry to reply so late 😥 . I hope I can spend some time researching about your issue and I'll try to give you an answer ASAP.
Thanks for your patience!!

[Lmsshepard]

Hello - thanks for replying and letting me know you are a bit behind. I have since created and extremely SIMPLE program to demonstrate the issue I am having. I created, under the same java8 / maven-build program configuration detailed in the posts above, a SIMPLE HELLO WORLD program to demonstrate the issue that I am having. The exact same results occur. I have attached all pertinent information for you to review. I appreciate your time and timely response as we have been stuck on this issue (and a related JRE bundle issue that I will post separately as to not to confuse this issue) for 3 months now and it is holding up our production. THANKS IN ADVANCE FOR YOUR DEDICATION AND TIME!

TerminalSignAndNotarizationChecks.txt

Terminal Launch Attempt - Error.txt

ConsoleLaunchError - Test2 Filter.txt

Test2 Build Output.txt

Info.plist.txt

pom.xml.txt

entitlements.plist.txt

[Lmsshepard]

I also would like to remind you that, as mentioned in the initial post, I am able to go into the apps Contents/MacOS folder and click on the universalJavaApplicationStub to launch the app that way. Hopefully that is a clue.... Thanks.