@mikecalbreeeezy commented on GitHub:
I'm having the same issue where it goes through the installomator script but doesn't update the browser so it gets stuck on the same version
@mjsanders commented on GitHub:
I see the same issue. I have used the appNewVersion from the labels online (4 months old) ` appNewVersion=$(getJSONValue "$(curl -fsL "https://versionhistory.googl…
@mjsanders commented on GitHub:
It really seems a temporary issue. (My guess a small difference in update repositories). I have removed Chrome, installed an old version (125.x) and ran the same…
@sslawter commented on GitHub:
Same issue trying to update from 131.0.6778.205 to 131.0.6778.265.
2025-01-08…
@AymenAbb commented on GitHub:
I couldn't replicate this issue on googlechromepkg. I had an older package installed (I didn't open it), then ran the installomator script using self service for…
@timnottom commented on GitHub:
@jakeolson613 can you check if this also works for you: https://github.com/Installomator/Installomator/pull/1702
@jakeolson613 commented on GitHub:
Just tested and worked perfectly on Apple Silicon. Will attempt to test on an Intel Mac later today or tomorrow.
Appreciate the work on this!
@jhawkinsgg commented on GitHub:
I've also created a PR for this #1956
@acodega commented on GitHub:
We'd recommend using the RSS feed instead, as was mentioned in your link from GitHub.
@PeterPlanlos commented on GitHub:
NEW VALUES for the ominssa API calls: product=omnissa_horizon_clients version=8
@acodega commented on GitHub:
Dup of #1946 which is linked to a PR fix
@spikehed commented on GitHub:
Actually your code was mostly there this is what should go into the PR.
vmwarehorizonclient)
name="VMware Horizon Client"
type="pkgInDmg"
…
@timnottom commented on GitHub:
Thanks @jhawkinsgg works perfectly fine!
@AymenAbb commented on GitHub:
Implement #1569 manually until a new version of installomator is out