XPC_ERROR_CONNECTION_INVALID from launchservice

By the way I uploaded the failing dmg here, just in case: https://github.com/molnard/WalletWasabi/releases/tag/macsign

Still a question! Anyone any idea?

I use this entitlements file on non-executables:

Just FYI, the entitlements for a process are set based on the entitlements of the main executable. Thus, these entitlements are ignored. Their presence is weird, but essentially benign.

I use this on executables (3 files)

Well, that’s definitely wrong. If you want the process to inherit its sandbox from its parent, you must have

com.apple.security.app-sandbox

com.apple.security.inherit

com.apple.security.inherit

com.apple.security.inherit

By the way I uploaded the failing dmg here

I downloaded that and took a look at your the entitlements of your main app:

% codesign -d --entitlements :- /Volumes/Wallet\ Wasabi/Wasabi\ Wallet.app 
…
<dict>
    …
    <key>com.apple.security.inherit</key>
    <true/>
</dict>
</plist>

You definitely need to get rid of

com.apple.security.inherit

Beyond that, I’m very concerned by your packaging. Consider this:

% ls -l "/Volumes/Wallet Wasabi/Wasabi Wallet.app/Contents/MacOS/" 
total 278808
-rw-r--r--@ … AvalonStudio.Shell.Extensibility.dll
-rw-r--r--@ … AvalonStudio.Shell.dll
-rw-r--r--@ … AvalonStudio.Utils.dll
-rw-r--r--@ … Avalonia.Animation.dll
…

The

Contents/MacOS

% ls -l@ "…/AvalonStudio.Shell.Extensibility.dll"
-rw-r--r--@ 1 quinn  staff  137216 13 Dec 14:06 …/AvalonStudio.Shell.Extensibility.dll
    com.apple.cs.CodeDirectory           216 
    com.apple.cs.CodeEntitlements        802 
    com.apple.cs.CodeRequirements        192 
    com.apple.cs.CodeRequirements-1      288 
    com.apple.cs.CodeSignature          9058

These extended attributes are present because these files are being signed as code but they can’t actually hold a code signature. As a result, the system dumps the code signature in extended attributes. This is very brittle.

Finally, yesterday I posted Signing a Mac Product For Distribution, which you’ll probably find useful.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Dear Eskimo,

Thank you for your detailed answer. From there I was able to make it work.

https://github.com/molnard/WalletWasabi/releases/download/v1.1.10.2-200204/Wasabi-1.1.10.2.dmg

However I could not restructure the dotnet core app folders as you described.
- I created symlinks with ln -s for every file but when I ran the executable I got missing file errors, dispite of that the symlink was there and working.

- I also tried exactly the same algorithm but with hardlinks (ln) then the application worked. Do you recommend to duplicate the files in this way? So for example put the dylibs into Framework directory and create a hardlink to it from MacOs directory? Now it is working without restructuring.
Dmg creation: is there a way to have the good old internet-enable feature with hdiutil?

One more thing that I could not solve is that now I got the message "App was downloaded from github... Open?". I press the Open button and for the first time nothing happens. On the second attempt the application just starts.

Thank you in advance,

Dave

I created symlinks with

ln -s

for every file but when I ran the executable I got missing file errors, dispite of that the symlink was there and working.

My experience is that macOS is good about following symlinks in this scenario. A while back I posted a concrete example of how to make this work on this thread. I’m not sure why it’s not working in your setup.

I also tried exactly the same algorithm but with hardlinks (ln) then the application worked. Do you recommend to duplicate the files in this way?

Hard links are not duplicates, but they can very easily turn into duplicates depending on the technique you use to archive and unarchive your app. I generally recommend that you avoid this.

is there a way to have the good old Internet-enable feature with

hdiutil

?

I don’t understand this. Please clarify why you mean by “Internet-enable feature”.

One more thing that I could not solve is that now I got the message "App was downloaded from github... Open?". I press the Open button and for the first time nothing happens. On the second attempt the application just starts.

That is very strange. I’ve not seen anything like that before. If you want to get to the bottom of this, I recommend you open a DTS tech support incident so that I can allocate the time needed to investigate.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Thank you for your answer.

I am jumping back to my original problem, unfortunately. It turned out that I made a typo and sandbox was not added - that why the error was solved (inheritance removed). https://github.com/zkSNACKs/WalletWasabi/blob/de503b6d2fee30a0cb849e389d0bdae5651802b0/WalletWasabi.Packager/Content/Osx/entitlements.plist

1. However, our current dmg package and app inside almost works as we would like to. There is only one message from the Gatekeeper: "The application was downloaded from the internet..." it looks like this: https://imgur.com/a/RDL5vfZ
   As far as I know, this Pop-up is normal and cannot be avoided - gatekeeper will always warn me that it is from the internet despite that it is properly signed and notarized. With our previous basic packager, we did not have the Open button so users had to go to system/security.
   You can see it for yourself by install and start this: https://github.com/molnard/WalletWasabi/releases/download/v1.1.10.2-200204/Wasabi-1.1.10.2.dmg
2. After pressing the Open button for the first time then app closed immediately. I have to click on the app again. After that, it will work without an issue. If you dragndrop the app from the dmg then again - it won't start for the first time.
3. Until now I opened the dmg dragndrop the app and close the dmg window. There was no new drive on the Desktop. Now there is the mounted image on the desktop until unmounting it - anyway it is not priority.
4. Symlinks are not working with dotnet-core app. So currently I see no way to make the folders OK.
5. With sandbox I am still getting the error mentioned above. There is a subcomponent that is trying to do things with launchservicesd. Can it be the problem? Shall we start to investigate there? Shall I send the report to DTS that was generated by the app?

Best regards,

David

As far as I know, this Pop-up is normal and cannot be avoided - gatekeeper will always warn me that it is from the internet despite that it is properly signed and notarized.

I can’t, alas, read the language in that alert but, yes, Gatekeeper will always present an alert if the app is quarantined. If the alert has a button that allows you to continue, that means Gatekeeper is happy. If not, you won’t be able to continue (you’ll either have an OK button that simply acknowledges the inability to continue or the Move to Trash and Cancel pair).

After pressing the Open button for the first time then app closed immediately.

See my answer above.

Symlinks are not working with dotnet-core app.

As I demonstrated above, symlinks should work just fine on the macOS side of things. It’s possible that your third-party runtime is not following them, although that would definitely be weird. It’s more likely that you didn’t set things up properly.

Either way, this is something you’ll have to pursue at you end, possibly in concert with your third-party runtime vendor. If you uncover evidence that Apple’s system software is doing the wrong thing with symlinks, let me know.

With sandbox I am still getting the error mentioned above.

I’m not entirely sure which error you’re referring to here.

Shall I send the report to DTS … ?

Yes. That’ll allow me to allocate more time to look at your various issues.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Dear Eskimo,

Before DTS I will investigate on our side. We might have a dependency that is trying to do something with launchservicesd.

Thank you for your help! I will get back here after that.

Best regards,

David