@adibue commented on GitHub:
Hey guys. I just observed exactly the same issue (running via Jamf Pro). However, the URL works just fine when using a web browser.
$ sudo jamf policy…
@Theile commented on GitHub:
Yes, same on my M1. It's a server-problem, mostly. Not sure we can do any kinds of workarounds, just for one label, but I leave this open, so you are welcome to seek…
@fleish commented on GitHub:
@Theile yes, the user has write permissions. Can you run these commands on your system to maybe sort out the differences?
Download: `curl --location --fail…
@fleish commented on GitHub:
Indeed, Monterey seems to be higher than both BigSur & my macports version:
curl 7.77.0 (x86_64-apple-darwin21.0) libcurl/7.77.0 (SecureTransport) LibreSSL/2.8…
@Theile commented on GitHub:
I'm on Monterey on a M1, maybe that version is newer. I reopened this issue, hopefully we can make a fix for this soon.
@TheDaveyBoy commented on GitHub:
I figured it out.
Change
displaydialog() { # $1: message $2: title
message=${1:-"Message"}
title=${2:-"Installomator"}
runAsUser…
@Raptor399 commented on GitHub:
Have look at Pull Request #140, which tries to solve the problem in a similar fashion, but makes the timeout configurable instead of hardcoded.
@scriptingosx commented on GitHub:
fixed in v8, thank you!
@Theile commented on GitHub:
I have corrected this in this PR: https://github.com/Installomator/Installomator/pull/317
@atillathec commented on GitHub:
Getting this same bug on my end, going to normal patch management of this app until this gets resolved
@fleish commented on GitHub:
@andrewchenWP can you expand on what "normal patch management" you are using for 1Password7?
@Apfelpom commented on GitHub:
To update 1Password error-free, all web browsers must be quit and especially the LaunchAgent must be stopped before. We use this PR https://github.com/Installomator/…
@Theile commented on GitHub:
Thank you for reporting this: It is now fixed in this PR: https://github.com/Installomator/Installomator/pull/317
@TheDaveyBoy commented on GitHub:
Do you know if this is still the behavior? If the user doesn't interact with the prompt, will the prompt kill itself and move on after a certain amount of time?
@Raptor399 commented on GitHub:
Also: does the user actually click "Not now", or do they leave the prompt open and just continue with their work?
Because the latter will never terminate the…
@acodega commented on GitHub:
Can't say off the top of my head, you could look at some old commits to see what it was, but I think at this point this issue can be closed if it's not being seen on…