Page 1 of 1

Detection issues in .NET API and Wurfl Cloud service

Posted: Mon Feb 20, 2012 2:12 am
by JackONeill
In Wurfl Cloud service I found two devices that I am no able to find using following user agents. DB API (TeraWurfl) finds them without a problem.
Mozilla/5.0 (Linux U Android 2.2 xx-xx GT-S5570 Build/FROYO) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1
Mozilla/5.0 (Linux U Android 2.2 xx-xx GT-S5830 Build/FROYO) AppleWebKit/533.1(KHTML, like Gecko) Version/4.0 Mobile Safari/533.1

I also tried the new .NET API (version 1.3.2) and there are six BlackBerry devices that I can't find while TeraWurfl finds them:
BlackBerry; U; BlackBerry 9360; es) AppleWebKit/534.11+ (KHTML, like Gecko) Version/7.0.0.353 Mobile Safari/534.11+
BlackBerry; U; BlackBerry 9780; en) AppleWebKit/534.1+ (KHTML, like Gecko) Version/6.0.0.131 Mobile Safari/534.1+
BlackBerry; U; BlackBerry 9800; en) AppleWebKit/534.1+ (KHTML, like Gecko) Version/6.0.0.135 Mobile Safari/534.1+
BlackBerry; U; BlackBerry 9810; xx-xx) AppleWebKit/534.11+ (KHTML, like Gecko) Version/7.0.0.313 Mobile Safari/534.11+
BlackBerry; U; BlackBerry 9860; xx-xx) AppleWebKit/534.11+ (KHTML, like Gecko) Version/6.1.0.76 Mobile Safari/534.11+
BlackBerry; U; BlackBerry 9900; xx-xx) AppleWebKit/534.11+ (KHTML, like Gecko) Version/6.1.0.55 Mobile Safari/534.11+

Re: Detection issues in .NET API and Wurfl Cloud service

Posted: Mon Feb 20, 2012 7:36 am
by luca.passani
Good Job, Jack. You spotted the delta between the last published API (1.3.X) and the new 1.4 which is what we run on our cloud in a virtually definitive form.

1.4 has loads of improvements: enhanced matchers and the ability to use WURFL to manage regular (mixed web-mobile) web traffic also on highly-trafficated websites.

Luca