MAC OS X上的单声道El Capitan：LSOpenURLsWithRole

Question

I have a .NET software which is running on Mono on both Linux and MAC. The software was packed as .app with Macpack on Mono 3.6.0 under OSX Lion and created an installer with PackageMaker. It worked fine on all new versions of OSX up until El Capitan which triggers the following error:

LSOpenURLsWithRole() failed with error -10810 for the file .../Applications/MyApp.app

I've moved the development files on El Capitan and managed to pack it with Macpack from Mono 4.0.4.4 . It doesn't seem to show that error when using

open -a MyApp.app

The only problem now is that it doesn't start on double-click. The software is installed in /Applications by the installer. It starts fine from console with open command but not on double-click. Is there a way I can see an error or something by emulating the double-click from console ?

PS. Also on El Capitan the only Mono framework that seems to work is the latest 4.0.4.4 or the one designed for El Capitan, 4.2.1. The new location for the binaries are in /usr/local/bin instead of /usr/bin and this works only if /usr/local/bin exists prior to installation, otherwise mono command won't be recognized.

Thanks

Answer 1

Same problem here (El Capitan). Thats how I solved (Mono 4.2.1)

1) Create an empty script and replace the one created by macpack (ex: KeePass.app/Contents/MacOS/KeePass)

2) Use full path for mono and for the exe file

#!/bin/sh
DIR=$(cd "$(dirname "$0")"; pwd) 
/usr/local/bin/mono $DIR/../Resources/KeePass.exe

I think thats somehow related to system-integrity-protection (csrutil) but not sure.

Answer 2

LSOpenURLsWithRole() failed with error -10810 for the file .../Applications/MyApp.app

Sounds like it might be permissions issue, but -10810 can mean a lot of things and I never have seen a response to that error number that is definitive as to its original (it has been around since PowerPC days). Permissions, external drive access and the actual Launch Services daemons have been pointed to.

• Reboot (or manually kill and respawn those services, including Finder/Spotlight)
• ls -l /Application/YourApp.app and check that is flagged as executable
• ls -l /Application/YourApp.app/Contents/MacOS/YourApp and check that is flagged as executable
• Open Console.app and retry double-clicking your app and review warnings/errors that are logged.
• ...

Moving to El Capitan? Then you need Mono version 4.2.x or 4.0.4.4.

From the Mono mailing list:

What is the difference between the latest Mono 4.0.4.4 package for Mac and the 4.2.1 El Capitan Preview? The changelog of 4.0.4.4 includes “33585: El Capitan System Integrity Protection support.” so i suppose that the 4.0.4.4 also works on El Capitan?.

Reply from Miguel de Icaza:

One is based on Mono 4.0 series, with minimal changes just to enable the support on El Capitan; The 4.2 has the same changes, on top of the latest Mono 4.2, available on Alpha and the release candidate.

Ref: http://sushihangover.github.io/osx-10-dot-11-el-capitan-which-mono-version/

Answer 3

Since there is no fix yet you can use this temporary fix. After packing with macpack open the app folder and go to /Contents/MacOS and edit the last if else from your launch script:

MONO_PATH="/usr/bin/mono"

cd "$APP_PATH/Contents/Resources"

if [ "$X11_MODE" -eq "1" ]; then
        open-x11 "$APP_NAME"
else
        if [ -f "/usr/local/bin/mono" ]; then MONO_PATH="/usr/local/bin/mono" ; fi
        "$MONO_PATH" "$ASSEMBLY"
fi