New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Chomre - new version detection not working #1543
Comments
You can reference the changes here that will help: #1366 Omaha proxy is dead, so switching to Google API is better |
Thanks for confirming, would you have any guidance for how to tell installomator to use Google API instead of Omaha proxy, do I need to to create my own version of installomator.sh & deploy to devices? |
There's 2 ways of doing that, best way imo you replace the problematic code which is in googlechromepkg.sh. The other is going with custom parameters but that's a bit more work. Go to your script and cntrl + f to find googlechromepkg, where it says appNewVersion= delete everything after the equals sign and set it to
ps that is grabbed from the linked thread |
The version detection for label googlechromepkg is not working.
When checking if an update is needed the output is:
" INFO : googlechromepkg : Latest version not specified."
This results in the installer being downloaded & installed even when the latest version is already installed.
Full output:
2024-03-12 11:29:03 : REQ : googlechromepkg : ################## Start Installomator v. 10.5, d
ate 2023-10-15
2024-03-12 11:29:03 : INFO : googlechromepkg : ################## Version: 10.5
2024-03-12 11:29:03 : INFO : googlechromepkg : ################## Date: 2023-10-15
2024-03-12 11:29:03 : INFO : googlechromepkg : ################## googlechromepkg
2024-03-12 11:29:03 : INFO : googlechromepkg : SwiftDialog is not installed, clear cmd file var
2024-03-12 11:29:03 : INFO : googlechromepkg : setting variable from argument NOTIFY=success
2024-03-12 11:29:03 : INFO : googlechromepkg : setting variable from argument BLOCKING_PROCESS_A
CTION=prompt_user_then_kill
2024-03-12 11:29:03 : INFO : googlechromepkg : setting variable from argument IGNORE_APP_STORE_A
PPS=yes
2024-03-12 11:29:03 : INFO : googlechromepkg : setting variable from argument REOPEN=yes
2024-03-12 11:29:03 : INFO : googlechromepkg : BLOCKING_PROCESS_ACTION=prompt_user_then_kill
2024-03-12 11:29:03 : INFO : googlechromepkg : NOTIFY=success
2024-03-12 11:29:03 : INFO : googlechromepkg : LOGGING=INFO
2024-03-12 11:29:03 : INFO : googlechromepkg : LOGO=/System/Applications/App Store.app/Contents/
Resources/AppIcon.icns
2024-03-12 11:29:03 : INFO : googlechromepkg : Label type: pkg
2024-03-12 11:29:03 : INFO : googlechromepkg : archiveName: Google Chrome.pkg
2024-03-12 11:29:03 : INFO : googlechromepkg : no blocking processes defined, using Google Chrom
e as default
2024-03-12 11:29:03 : INFO : googlechromepkg : App(s) found: /Applications/Google Chrome.app
2024-03-12 11:29:03 : INFO : googlechromepkg : found app at /Applications/Google Chrome.app, ver
sion 122.0.6261.112, on versionKey CFBundleShortVersionString
2024-03-12 11:29:03 : INFO : googlechromepkg : appversion: 122.0.6261.112
2024-03-12 11:29:03 : INFO : googlechromepkg : Label is not of type “updateronly”, and it’s set
to use force to install or ignoring app store apps, so not using updateTool.
2024-03-12 11:29:03 : INFO : googlechromepkg : Latest version not specified.
2024-03-12 11:29:03 : REQ : googlechromepkg : Downloading https://dl.google.com/chrome/mac/stab
le/accept_tos%3Dhttps%253A%252F%252Fwww.google.com%252Fintl%252Fen_ph%252Fchrome%252Fterms%252F%2
6_and_accept_tos%3Dhttps%253A%252F%252Fpolicies.google.com%252Fterms/googlechrome.pkg to Google C
hrome.pkg
2024-03-12 11:29:07 : INFO : googlechromepkg : found blocking process Google Chrome
2024-03-12 11:29:33 : INFO : googlechromepkg : Installomator did not close any apps, so no need
to reopen any apps.
2024-03-12 11:29:33 : ERROR : googlechromepkg : ERROR: user aborted update
2024-03-12 11:29:33 : REQ : googlechromepkg : ################## End Installomator, exit code 1
The text was updated successfully, but these errors were encountered: