Widevine chrome://components/ update mechanism.

[C.C]

Hi 

I would like to enable Widevine chrome://components/ update mechanism.

I can see in the code, the sample update xml is as follows.

// An app element looks like this:

//    <app appid="hnimpnehoodheedghdeeijklkeaacbdc"

//         version="0.1.2.3" installsource="ondemand">

//      <updatecheck />

//      <packages>

//        <package fp="abcd" />

//      </packages>

//    </app>

In the log, it reports no update is available.

No update available for CRX: oimompecagnajdejgnnjijobebaeigek

[5540:2932:0910/162644:VERBOSE1:action_update_check.cc(187)] Update check completed but no update is needed.

[5540:2932:0910/162644:VERBOSE1:component_updater_service.cc(301)] Update completed with error 0

Is there a magic version number I need to send or is it forbidden to access Googles update

server like this?

Thanks

[David Dorwin]

It's possible that some combination of data in the update check does not match a rule. What platform is this? Did you modify widevine_cdm_component_installer.cc or any other code? Did you change the Chromium product version or channel names?

David

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[C.C]

Hi David

So far I have modified the widevine_cdm_version.h to enable widevine 

and to include the version information.

I have not modified the widevine_cmd_component_installer.cc or any other

parts of the widevine adapter component.

I have changed the product version and I am on the dev channel.

However, the message that gets sent to the server only appears to include 

the current widevine version and crx component id. 

So I figure it must be something to do with the version, I have now tried 

"1.0.123.456" -->This is the default when WIDEVINE_CDM_VERSION_STRING is uncommented. 

"0.0.0.0" -->I just thought this might work.

"1.4.8.824" -->This is currently in chrome.

It would be great to download this component within the browser as it is 

required to watch DRM protected videos.

[David Dorwin]

Since the update rules depend on the browser version in the update request, changing the product version would probably break the update checks. The version in the update request really needs to match the Chromium/Chrome version or any CDM installed might be incompatible with the browser. Even if it worked today, future incompatibilities might be introduced.

Is WIDEVINE_CDM_IS_COMPONENT defined? If it is defined, you should not need WIDEVINE_CDM_VERSION_STRING. If it isn't and you need WIDEVINE_CDM_VERSION_STRING, then the Widevine component installer shouldn't be compiled.

--

[C.C]

Thanks a lot David, it was the product version information. I can now receive the plugin.

On Thursday, September 10, 2015 at 4:29:58 PM UTC+1, C.C wrote: