What you may be missing is that the update path is hardcoded into the
extension manifest.
A common mistake is to change the path you are using in the
ExtensionInstallForcelist policy, but you have to realise that any CRX
that was already installed with that extension ID is going to look at
the previous path (the one in the manifest). In my opinion, this is a
bad design, but this is the way it's been for...oh...a decade.
By deleting the extension you force Chrome to re-read the policy and
use the new path.
Another trick for this is to create a new extension ID for your
extension, that way you can use the new ID and any path you want,
regardless of what has been installed, because Chrome will remove the
old extension and install the new one with the new ID and path.
> --
> You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
chromium-extens...@chromium.org.
> To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/97d7035b-913b-49d9-a67a-6a114b945666n%40chromium.org.