First off, thank you so much for this script. I've modified it for my organization and it works amazing.

This is more of a question than a bug. How are you able to figure out the icon URL for the macOS releases? Looking to add the Sonoma icon to this part of the code:

declare -A macosIcon=(
    [13]="https://is1-ssl.mzstatic.com/image/thumb/Purple126/v4/01/11/29/01112962-0b21-4351-3e51-28dc1d7fe0a7/ProductPageIcon.png/460x0w.webp"
    [12]="https://is1-ssl.mzstatic.com/image/thumb/Purple116/v4/fc/5f/46/fc5f4610-1647-e0bb-197d-a5a447ec3965/ProductPageIcon.png/460x0w.webp"
    [11]="https://is1-ssl.mzstatic.com/image/thumb/Purple116/v4/48/4b/eb/484beb20-2c97-1f72-cc11-081b82b1f920/ProductPageIcon.png/460x0w.webp"
    )
    iconURL=${macosIcon[$majorversion]}

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

jss-progress.sh scriptlog variable is wrong on line 30. it should be $scriptLog.

I just discovered swiftDialog and I am honestly as thrilled as the proverbial kid in candy store!! Thank you for this awesome app!
I was wondering if you might consider adding a Select File button feature? (similar to AppleScript's "choose file") Thank you.

Due to some latency with Jamf, I found that there is a potential situation where a properly scoped Self Service policy with the jss-progress.sh script could hang indefinitely if the policy it calls is no longer in scope. This results in the progress bar window being stuck on screen with no obvious way for the end user to force quit it.

Reproducibility: Anytime the jss-progress.sh policy has a trigger for a policy that does not include the machine the jss-progress.sh policy is being run on.