Couldn't communicate with a helper application #172
marcusheBG
started this conversation in
General
Replies: 1 comment
-
As we're unable to reproduce the issue, I'm transitioning this to a discussion thread where individuals can share their experiences. Additionally, I've established a new wiki page dedicated to tracking these sporadic issues, which are likely resultant from macOS anomalies or incorrect workflows. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
Receiving
"Notification Agent rich notification authorization request ended with error: Couldn't communicate with a helper application"
on recently deployed machines with signed custom complied app (not notarized)Mosyle MDM
Experienced on a 12.6.1 and 13.2.1 Mac. ~95% of other Macs in environment working appropriately.
Tried reapplying notifications profile with reinstall profile button in MDM, no luck
Tried
sudo -u $currentUser
, no luckTried
launchctl asuser $currentUserUID
, worked!After running once with
launchctl asuser
, reverting script to running notifier without arguments was working properly and providing notification.Most Macs in MDM working, some need a "jumpstart" with
launchctl asuser
. For now, leavinglaunchctl asuser
in our scripts.....Desktop (please complete the following information):
Additional context
Running from Mosyle MDM. Most machines work without
launchctl asuser.
Some need a jumpstart. Just leavinglaunchctl asuser
in our scripts for now so we may not see the bug again to report more.Thank you!
Beta Was this translation helpful? Give feedback.
All reactions