nudge: JAMF Self-Service URI Broken in 1.1.14.X

I have been in the process of upgrading my fleet of Macs to the latest version of Nudge. We are also in the process of attempting to upgrade users by having them directed to a Self-Service policy in JAMF (we have renamed our JAMF app to Software Center). While testing Nudge with this new workflow, I have found that the URI functionality to direct a user to a policy in Self Service does not work. Or rather, I should say that Nudge crashes when I attempt to use this functionality:

2024-02-23 11:21:00.155527-0800 localhost Nudge[14234]: [com.github.macadmins.Nudge:user-interface] Unable to find major upgrade application, exiting Nudge

We have tested this with older versions of Nudge (1.13 and older) and it seems to work fine. To be specific, here is the plist key:

<key>actionButtonPath</key> <string>jamfselfservice://content?entity=policy&id=2237&action=view</string>

Let me know if you need any further information.

About this issue

Original URL
State: closed
Created 4 months ago
Comments: 18 (11 by maintainers)

Most upvoted comments

I think I have discovered that it is a mix of several keys being set in different out of box configurations that lead to this not working, specifically attemptToFetchMajorUpgrade with actionButtonPath for major upgrades.

When in this case, new logic was written to exit Nudge because of the primary keys not being set and nudge’s backup files being set. With this new build, I will now warn about this behavior because it is still non-ideal from a major upgrade, but that the admin has created their own set of workarounds.

Please try https://github.com/macadmins/nudge/releases/tag/v1.1.14.81549

erikng on Feb 27, 2024

If I make it 15.99.99, I receive the same message, as Nudge cannot understand how to enforce this event without additional keys being set.

erikng on Feb 26, 2024

I am able to use actionButtonPath on the latest release but I have a suspicion you are running on macOS 13 or lower and attempting to go to a major upgrade version. Is that the case?

I see you are putting the key in the exact same spot in my test (within osVersionRequirements).

My test was a macOS 14.3.1 device pretending to update to 14.99.99

erikng on Feb 26, 2024