OS X application won't launch with jigsaw

Michael Hall mik3hall at gmail.com
Sun Nov 29 21:20:10 UTC 2015

>> On Nov 25, 2015, at 10:45 AM, Danno Ferrin <danno.ferrin at oracle.com <mailto:danno.ferrin at oracle.com>> wrote:
>> However, we fully expect that the Java 8 packager will not be able to make bundles holding a Java 9 runtime, and I think this is what you are encountering.

I got past the original, jigsaw problem with internal apple api’s, running with a command line launch from a shell script. 
when I tried applying the same change, addition of a new -X jvmoption to my application bundle by changing the Info.plist file with Xcode, I get this…

11/29/15 3:00:35.131 PM sandboxd[277]: ([6613]) mdworker(6613) deny file-read-data /Users/mjh/Library/Preferences/com.apple.security.plist (import fstype:hfs fsflag:480D000 flags:250000025E diag:0 isXCode:0 uti:com.apple.application-bundle plugin:/Library/Spotlight/Application.mdimporter - find suspect file using: sudo mdutil -t 12638960)
11/29/15 3:01:14.467 PM amfid[104]: /Users/mjh/HalfPipe/bundles/HalfPipe9/HalfPipe9.app/Contents/MacOS/HalfPipe9 signature not valid: 0xfffefa2a
11/29/15 3:01:14.000 PM kernel[0]: proc 6707: load code signature error 4 for file “HalfPipe9"

It might be that changing the application bundle doesn’t invalidate the signed application signature but changing the Info.plist does?
I might try regenerating the application including the -X option.

I assume from your message javapackager support for Java 9 isn’t considered complete yet? So I might have to try the same trick of generating a earlier version and then copying in the java 9 jvm. My use of javapackager is still rather limited as for this application reusing the same one has seemed to work best up to now. 

Michael Hall

More information about the jigsaw-dev mailing list