nudge: Traditional LaunchAgent doesn't load with 1.1.12.81501
After updating to Nudge 1.1.12.81501 on macOS 14 Sonoma the traditional LaunchAgent no longer loads on boot/login.
/bin/launchctl list | grep Nudge
no longer shows the LaunchAgent as loaded.
/bin/launchctl load /Library/LaunchAgents/com.github.macadmins.Nudge.plist
returns success, but does not actually succeed in loading the LaunchAgent.
Installing the Nudge_LaunchAgent-1.0.1.pkg
package does not result in the LaunchAgent being loaded.
Double-clicking Nudge.app
however does load the LaunchAgent. After that launchctl list
shows it as loaded.
However after a reboot it is unloaded once again.
I have tested this scenario with a configuration profile requiring 14.99 and Nudge never launches on it’s own. Opening Nudge manually results in the expected behavior, but if you select a deferral option or reboot the LaunchAgent is no longer loaded.
The Nudge Logger LaunchDaemon works as expected.
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Reactions: 9
- Comments: 47 (30 by maintainers)
@BigMacAdmin has also shared that he has found greater success by having a pause between the complete removal and the reinstallation.
After testing with @kevinmcox and a few others on Slack, the following issue still exists:
Case 1
HOWEVER, if you have 1.1.12 already installed, the following is true:
Case 2
I’m with @tuxudo on that - while it worked fine for my fleet to run
resetbtm
, I don’t know it would necessarily be true universally. Would a release notes mention or similar be sufficient? If you do want to put this in the pkg, I would suggest doing it preinstall so the script can detect if the machine is upgrading from an affected release or not so it is more surgical applying the reset.I think the
resetbtm
will have negative impacts for end users. During initial troubleshooting I tried it and it cleared out all of the open at login apps from my test user account. The daemons/agents were also cleared out, but they returned after a restart. More testing is needed to determine if this is limited to just my Mac or that’s the expected behavior.Unless Apple have made changes since June (I haven’t checked) SMAppService documentation overstates how useful it is for system utilities unfortunately.
I really need to follow up with them about it now Sonoma is out and talk to someone that actually works on the thing.
Thanks for confirming. I am highly suspect of the issue being the new nudge version and is something else.
There have been reports of nudge not launching if you upgrade from a version with the old cert to the new cert. I wonder if that’s what is happening here.