Menu

#648 Can't build / run on Mac OS 10.12 (Sierra)

v4.8.0
closed-works-for-me
nobody
None
5
2018-06-16
2017-07-21
No

I just built from source, and can't get this to run on Mac OS 10.12.5.

You can't disable gatekeeping in Mac OS Sierra (10.12) so I signed the build:

codesign --force --verify --verbose --sign "Developer ID Application: blah blah" dist/DavMail.app/Contents/MacOS/libgrowl.jnilib
dist/DavMail.app/Contents/MacOS/libgrowl.jnilib: signed Mach-O universal (i386 ppc7400 x86_64) [libgrowl]

codesign --force --verify --verbose --sign "Developer ID Application: blah blah" dist/DavMail.app
dist/DavMail.app: signed app bundle with generic [DavMail]

Then tried to run it, but it doesn't appear...

Opened console to check for errors...

Initially I got this error:
Jul 21 17:41:09 haswell com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x10000003.davmail[8506]): Could not find and/or execute program specified by service: 13: Permission denied: /Users/abarrett/Documents/davmail-src/davmail-4.8.0/dist/DavMail.app/Contents/MacOS/davmail

So I checked, and it's a bourne shell script with bad permissions:
ls -la dist/DavMail.app/Contents/MacOS/
total 280
drwxr-xr-x 4 abarrett staff 136 21 Jul 17:40 .
drwxr-xr-x 7 abarrett staff 238 21 Jul 17:40 ..
-rw-r--r-- 1 abarrett staff 21165 12 Jul 15:35 davmail
-rw-r--r-- 1 abarrett staff 117264 21 Jul 17:40 libgrowl.jnilib

file dist/DavMail.app/Contents/MacOS/davmail
dist/DavMail.app/Contents/MacOS/davmail: Bourne-Again shell script text executable, UTF-8 Unicode text, with very long lines

chmod 755 dist/DavMail.app/Contents/MacOS/davmail

Now I try it again, and more errors, and I'm stuck now...

Jul 21 17:42:46 haswell com.apple.xpc.launchd[1] (com.apple.auditd[8526]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd
Jul 21 17:43:48 haswell com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x10000004.davmail[8548]): Service exited with abnormal code: 1

Discussion

  • Mickael Guessant

    Thanks for your feedback, some more info:

    • the shell script is just universalJavaApplicationStub renamed, see:
      https://github.com/tofi86/universalJavaApplicationStub

    • the 755 chmod is automatically applied at packaging step

    • the shell script has unix line feeds, you should be able to edit it with the right editor
    • can you launch the application manually ?

    You can get full command line by just changing exec to echo at the end of the shell script

    As the actual launcher is java, not the shell script, I would also check that Java latest version is installed.

     
  • Mickael Guessant

    • status: open --> pending-works-for-me
     
  • Mickael Guessant

    • status: pending-works-for-me --> closed-works-for-me
     

Log in to post a comment.

Monday.com Logo