The depnotify.log must end up with the escaped carriage returns (\n's) in it, so the script needs to better escape the 's or it will put carriage returns into the file. I've ended up having to change the script to put them as \\n instead of \n.
I've been noticing my MAIN_TEXT only showing the first line in the dialog, and discovered the issue was because the \n's would go into depnotify.log translated to carriage returns, when depnotify.log requires the \n's.
I've been seeing this on macOS 10.15 and above, with DEPNotify 1.1.6 (I'm not using dev on macOS 10.14 or earlier, as we are treating 10.14 and earlier as unsupported).
The depnotify.log must end up with the escaped carriage returns (\n's) in it, so the script needs to better escape the 's or it will put carriage returns into the file. I've ended up having to change the script to put them as \\n instead of \n.
I've been noticing my MAIN_TEXT only showing the first line in the dialog, and discovered the issue was because the \n's would go into depnotify.log translated to carriage returns, when depnotify.log requires the \n's.
I've been seeing this on macOS 10.15 and above, with DEPNotify 1.1.6 (I'm not using dev on macOS 10.14 or earlier, as we are treating 10.14 and earlier as unsupported).