Document detection and pings for overinstalls
Add documentation to the updater's functional spec explaining how external installs are periodically detected and pinged. Bug: 397415614 Change-Id: I9f046e0c77f5bf7139fe0af04125f3d5258b6a7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6278790 Reviewed-by: Sorin Jianu <sorin@chromium.org> Commit-Queue: Noah Rose Ledesma <noahrose@google.com> Cr-Commit-Position: refs/heads/main@{#1421665}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
a6252eb75b
commit
1c0ad55f18
@ -521,6 +521,20 @@ button. Clicking the help button opens a web page in the user's default browser.
|
||||
The page is opened with a query string:
|
||||
`?product={AppId}&errorcode={ErrorCode}`.
|
||||
|
||||
### Periodic detection of over-installed apps
|
||||
|
||||
The updater periodically checks if application versions persisted to the system
|
||||
match its built-in `pv` value. If different, the updater sends an installation
|
||||
ping for the application indicating the actually installed version and updates
|
||||
the internal `pv` value to match.
|
||||
|
||||
The application's version persisted to the system is determined via:
|
||||
|
||||
* The plist file and key indicated by the `pv_path` and `pv_key` in the app's
|
||||
updater registration on MacOS.
|
||||
* The `pv` registry key as described by the "App Registration" section on
|
||||
Windows.
|
||||
|
||||
## Updates
|
||||
There is no limit for the number of retries to update an application if the
|
||||
update fails repeatedly.
|
||||
|
Reference in New Issue
Block a user