O4 isn't updating; q on updates disabled

[John Mevissen]

Hi friendly updater devs,

My O4 is still on build 5594 (from the 13th, according to chromiumdash), I assume new builds haven't been published for a few days? Chrome is up to 5598.

---

On-demand checks for both my (system) Chrome and (user) Chrome Canary are sending the updates-disabled flag, so I'm not getting on-demand updates. Any idea why that is happening? It seems undesirable. (Or maybe O4 doesn't support on-demand checks yet?)

E.g.:

[15732:9348:0215/162311.521:VERBOSE2:app_server.cc(68)] This version: 112.0.5594.0, active version: 112.0.5594.0

...

[15732:9348:0215/162311.540:VERBOSE2:network_fetcher.cc(268)] {"request":{"@os":"win","@updater":"updater","acceptformat":"crx3","app":[{"appid":"{8A69D345-D564-463c-AFF1-A69D9E530F96}","cohort":"1:gu/i19:","cohortname":"Stable Installs & Version Pins","enabled":true,"installsource":"ondemand","packages":{"package":[{"fp":"1.4fafd7a48cc4d90d8fd4238812032904da271becc366f2e7b1de97f90a6e6c1b"}]},"ping":{"ad":5889,"ping_freshness":"{9229d4f7-04ca-4fff-9743-9470b5fda0ea}","rd":5889},"updatecheck":{"updatedisabled":true},"version":"110.0.5481.100"}],"arch":"x86","dedup":"cr","domainjoined":false,"hw":{"avx":true,"physmemory":16,"sse":true,"sse2":true,"sse3":true,"sse41":true,"sse42":true,"ssse3":true},"ismachine":true,"nacl_arch":"x86-64","os":{"arch":"x86_64","platform":"Windows","version":"10.0.19045.2486"},"prodversion":"112.0.5594.0","protocol":"3.1","requestid":"{38b753fa-2ed0-4a24-8280-db913643f165}","sessionid":"{048adb49-7c9b-411f-830c-d2744488608e}","updaterversion":"112.0.5594.0","wow64":true}}
[15732:9348:0215/162311.648:VERBOSE2:network_fetcher.cc(433)] )]}'
{"response":{"server":"prod","protocol":"3.1","daystart":{"elapsed_seconds":58992,"elapsed_days":5889},"app":[{"appid":"{8A69D345-D564-463c-AFF1-A69D9E530F96}","cohort":"1:gu/i19:","status":"ok","cohortname":"Stable Installs \u0026 Version Pins","ping":{"status":"ok"},"updatecheck":{"status":"noupdate","info":"disabled by client"}}]}}

John

[S Ganesh]

Hi John(!), the `updatedisabled:true` is a new aspect of the updater, meant to allow checking for updates without update_client applying the updates. The server is still expected to send the current serving version in the update response, so I'm not sure what's happening. I expect Josh has the answer for this one.

[Sorin Jianu]

John, thank you for reporting this, I believe we broke the backward compat with the ondemand API, and consequently Chrome ondemand is not working right now.

--
You received this message because you are subscribed to the Google Groups "Chrome Updates Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-updates-...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-updates-dev/82a5d669-e08d-4d58-8056-5250a3c112bcn%40chromium.org.

[Joshua Pawlicki]

Regarding O4 being on 5594, yes; we haven't published a new one in a bit due to some issues with the signing pipeline.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-updates-dev/CACdEVSy_ypQKJ%2BsRsm28F9bYXt%2BcNMb5a0-_B4puJKWqRyY50w%40mail.gmail.com.

[John Mevissen]

This (O4 updating and on-demand checks) started working again this week. Thank you!

John

[Sorin Jianu]

Great news, thank you, no kidding, we are about to break these again.