Blackberry - patch.xml

[gwV6Nt9ntUZijaq]

We use a product called Ektron that implements WURFL, so unfortunately, the WURFL is sort of a black box to us. I tried creating a patch file for these missing user agents. I am not sure if the syntax is valid. I was hoping to have the "fall_back" work, but I am not sure if I have right.

Does this look right? The User agents themselves are missing so I would like to submit them also. -- Thanks Peter

<wurfl_patch>
<devices>
<device id="blackbery9330_6522" user_agent="Mozilla/5.0 (BlackBerry; U; BlackBerry 9330; en-US) AppleWebKit/534.8+ (KHTML, like Gecko) Version/6.0.0.522 Mobile Safari/534.8+" fall_back="blackberry_generic_ver5" actual_device_root="true">
<group id="product_info">
<capability name="device_os_version" value="6.0.0.522"/>
<capability name="model_extra_info" value="6.0.0.522"/>
<capability name="release_date" value="2011_november"/>
</group>

</device>
<device id="blackberry9650_ver1_subos6415" user_agent="Mozilla/5.0 (BlackBerry; U; BlackBerry 9650; en-US) AppleWebKit/534.1+ (KHTML, like Gecko) Version/6.0.0.415 Mobile Safari/534.1+" fall_back="blackberry9650_ver1">
<group id="product_info">
<capability name="mobile_browser_version" value="6.0"/>
<capability name="device_os_version" value="6.0"/>
</group>
</device>
</devices>
</wurfl_patch>

[kamermans]

Are you able to figure out which API they have embedded in the product? As you can see from the Official DB API, both of these user agents are matching properly:

http://bit.ly/nOdsW4
http://bit.ly/pIumMq

As for your patch file, the format looks correct, yes.

[gwV6Nt9ntUZijaq]

Sorry, I have no idea what API they have embedded. I had to update a web.config in order to specify the location of the path file.

I am trying WURFL 2.2 now.

Thanks

Peter

[gwV6Nt9ntUZijaq]

Another Blackberry user agent:

Mozilla/5.0 (BlackBerry; U; BlackBerry 9930; en-US) AppleWebKit/534.11+ (KHTML, like Gecko) Version/7.0.0.241 Mobile Safari/534.11+

[kamermans]

This user agent is also being matched properly: http://bit.ly/r3KSFr

There must be something going on under the hood that is causing these detection problems.