Hangs when "Jamf policy" or "Jamf recon" are the target policies

[diwanicki]

I have this setup to call secondary policies via custom trigger. Those policies run "Jamf policy" or "Jamf recon" as execute commands. The dialog progress bar moves but the text disappears after the first log entry, then both the dialog and Self Service hang.

It's like the script loses track of the active PID?

These are the two major pain points where user feedback would be super helpful. I have not tested with a standard installation as we generally don't use Self Service installs. This was tested on Ventura 13.2 with the latest swiftDialog 2.1 RC 3

[howieisaacks]

I am seeing this behavior too. I wanted to use this for installs that involve large software packages that take a while to either download or install. It looks great but it hangs at the end. I ended up having to go into Activity Monitor to kill Swift Dialog. The policy ran just fine including an inventory step. I'm going to try to figure out how to stop this. If I can, I'm happy to post the solution here.

[bartreardon]

what script are you using? (there are a few in the repo, most will need updating as they were written as examples for very early versions of swiftDialog)

[howieisaacks]

Thanks for the fast reply! The script I used yesterday to test is the one located here:

https://github.com/bartreardon/swiftDialog-scripts/blob/main/JamfSelfService/jss-progress.sh

This is great work! I was going to write something myself to work with Swift Dialog, but I'm new to working with Swift Dialog so I tried your script to see if it would work for me. I wanted something to display a status to a user who is running a macOS install from Self Service. Your script would work well for any Self Service policy that involves a large package download or long install process.

[howieisaacks]

I have spent hours working with this script today. The progress either stalls in the middle long after the download has completed or it finishes but the Dialog window never goes away. I have to quit it using Activity Monitor. I am not using a recon step at all anywhere. Perhaps what I am doing with my policy is the problem so I'm going to try doing this differently. I see no errors in the log file. I wrote a script a couple of months ago that will download a macOS installer using the link to download the Install Assistant package. The script uses curl to do this. Once the package is downloaded, the script runs the package to put the macOS install app in Applications. This works perfectly when I add it to a policy. I wanted to have a progress window for users to know what is happening since Self Service does not provide any status except a spinning indicator under the policy icon. I am right now uploading the Install Assistant package to Jamf Pro... all 12.96GB of it to try to deploy the installer that way. I'm trying to give my Mac support team access to the latest developer beta of macOS Sonoma. I didn't want to have to upload this huge package to Jamf Pro. I wanted their computers to do the work of downloading. I have done this with large packages before so I know this works.

[bartreardon]

I reckon you're coming up against jamf thinking the policy is still running. it's an issue I hit up against a couple of times.