Post not yet marked as solved
The standard solution is to mark the app as a UI element (via the [LSUIElementproperty][refLSUIElement]) but that prevents it from showing up in the Dock or having its own menu bar. I can still display a status bar item just fine.
Any alt option in xcode so that we can still have the app icon appear in Dock , even if it is a status bar item, but prevent the Crash Report UI ?
Please post the final launchd property list that you settled on.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key>
<dict>
<key>Crashed</key>
<false/>
<key>SuccessfulExit</key>
<false/>
</dict>
<key>Label</key>
<string>com.cirrusthinking.dollyappd</string>
<key>LimitLoadToSessionType</key>
<string>Aqua</string>
<key>MachServices</key>
<dict>
<key>com.cirrusthinking.dollyappd</key>
<true/>
</dict>
<key>ProgramArguments</key>
<array>
<string>open</string>
<string>-W</string>
<string>/Applications/DollyDrive.app</string>
</array>
</dict>
</plist>
Post not yet marked as solved
The "app" is displayed in the Dock, its a GUI and a Status Bar item.
We where able to resolve the issue by adding an extra key in the plist
<key>MachServices</key>
and
<key>Crashed</key>
<false/>
Still, the man pages are not enough to decipher all different options available and there is not enough documentation on the Apple developers site to well define the xml logic according to various MacOS version need. ....
Post not yet marked as solved
I have tried all of these on M1 with no success so far. After unloading the plist and running launchctl print we still see the labeled in a disabled format. Load and unload do not seem to work in Monterey M1 . The label is loaded but after a crash or force quit the app does not restart properly. All we get is the Problem Reporter ui reporting the crash and asking to reopen but launchctl does not restart the app
Yes tried it and it did not work for me .
Thank you !We will test this and verify it corrects the issue.But this does not correct the fact that when verifying the codesignature for the XPS service it shows up as rejected (the code is valid but does not seem to be an app). Or is this response normal when verifign and xpc service ?
ok so doing some further test what is happening when launching the app that is codesigned for the first time.The XPC service needs to access the main.app keychain Username and Password in order to then chat with web services. When the app is first installed there is an OS allert indicating that XPC is trying to access the Main.app keychain entry , [Always Allow] [ Deny] [Allow] . I would like to avoid this step so that the XPS service is allowed automatically and user does not need to provide input. if XPC is a target of the same app wouldd the system see it as part of it and not have to ask ?My initial thought is that the system is asking to allow the entry because the XPC services are not certified correctly but maybe there is more or something different to it ?Anyone ?
Tat is exactly what was needed.Thank You !Te run loop hint helped us look at some posted documentation and pointed us in the correct direction.https://stackoverflow.com/questions/21937504/using-fseventstream-within-xpc-service-does-not-work
