Can you grab and attach the logs with the ksdiagnostics tool:

/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics

If the tool is not there, prefix the path above with '~' (user Keystone).

In general, we are running tests regularly on High Sierra and so far no issues:
http://shortn/_tcQwbvj4bn (functional) and http://shortn/_INvsVyQNgV (unit tests). The only failures are timeouts due to oversubscribing of the VMs.

Diagnostics file attached.

Deleted: KSDiagnostics-521655451.195954.zip 57.1 KB

KSDiagnostics-521655451.195954.zip 57.1 KB Download

Thanks, Jason. It seems like from Keystone point of view, you have stable installed on that machine. Observe the cohortname in the request. The server correctly responded with no update. Any chance you have both beta and stable installed on the same machine?


			<request protocol="3.0" version="KeystoneAdmin-1.2.8.57" ismachine="0" requestid="{A278FB9D-D785-4CE3-9B81-C6BFDD6C5713}" dedup="cr" sessionid="{71785514-F88F-4E83-89F4-2426C47E0FEB}" installsource="ondemandupdate">
			    <os platform="mac" version="10.13" arch="x86_64h" sp="10.13.0_x86_64h"></os>
			    <app appid="com.google.Chrome" version="59.0.3071.115" cohort="1:1y5:" cohortname="Stable" lang="en-us" installage="42" brand="CHFA" signed="1">
			        <ping r="-1" rd="-1"></ping>
			        <updatecheck></updatecheck>
			    </app>
			</request>

I have both installed (same as on my everyday laptop). Day-to-day I run Chrome Mac Beta, which I've placed in ~/Applications/GoogleChromeBeta.

But Keystone does not support that yet. We have a single ticket for Chrome, so we will always update only one of them, typically the first one that registered itself with Keystone. I just filed internal b/63667295 to add support.

I have been running Chrome in this configuration, on multiple machines, for more than a year. In all cases, Chrome stable was installed on the machines first, and then Chrome Beta. And, on my machines where I've been running Chrome Beta and the Google Updater has said I need to update my version of Chrome Stable, I have at least once just launched the stable version to get it to update itself.

Are you saying that if I have Chrome Stable and Chrome Beta installed, that if I go to About Chrome in each those channels, one of them will show new updates but the other one will never show that it needs to be updated? It seems like no matter what, if I visit About Chrome in any version, that should force that copy of Chrome to look for a newer version.

So now, after throwing Stable channel Chrome into the trash and emptying the trash I get the following error:

Deleted: Screen Shot 2017-07-13 at 11.02.25 AM.png 57.5 KB

	Screen Shot 2017-07-13 at 11.02.25 AM.png 57.5 KB View Download

I stand corrected about the multichannel support. Even Windows version does not support it. Instead, on Windows builds Chrome has separate appids for Stable and Beta. The same should be done for the Mac builds. 

Next, I believe that the error you are experiencing is temporary, as the ticket will be deleted the next time Keystone runs. You can speed this up by running it manually:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/CheckForUpdatesNow.command

Try doing that and then restart the Beta to see if you still experience the error.

Issue 373987 covers the Mac work for side-by-side install, but right now we do not officially support it (only Canary can be SxS).

Hi borisv@,

I ran the command in c#11 and Chrome is updating correctly now. I wonder (a little) how it is that things are working correctly on my regular laptop.