Hi Dan,

Awesome! Do let us know if you have any additional questions.

Cheers!

Hi Dan,

The WURFL API type you are looking for is the DBAPI aka Tera-WURFL. You can go ahead and delete the PHP API. To re-iterate, this is the WURFL API you need.

Cheers!

Hi Dan, WURFL does detect both the Samsung Galaxy S4 from Verizon and the HTC One perfectly. Let me ask you a few questions so that we can figure out what's going on. The newest publicly version of the WURFL.xml file was released in October 2013, so you are definitely running an old WURFL.xml file a...

Hi Chris,

No issues. We will definitely let you know when it's updated.

Cheers!

Hi,

Thank you for the information. Our support team is looking into this and we will keep you updated on this issue.

Thanks again and cheers!

Hi Chris, To add to our reply above, we added the Nexus 5 user-agent last week and should have come out in the last weekend's WURFL.xml release. If you are a customer, please make sure you are on the latest WURFL.xml snapshot available for your account . This device should also be detected on the WU...

Hi, The UAs you've posted seem to have been modified by some tool, prepending the device's brand name and model name to the UA. So the UAs from your post are in the form of Brand_Name Model_Name<tab><>UA. Here's an example of this discrepancy: UA from your post: Samsung S390 SAMSUNG-SGH-S390G[TF3597...

Yes, that is correct. We introduced the logic for MSIE 11 detection with the WURFL API v1.5. Glad everything's worked out fine.

Cheers!

Awesome! Do let us know if we can assist you in anyway.

Cheers!

Hi,

The WURFL API already supports and detects MSIE 11 User-Agents. You can verify that by visiting here and here.

These results don't show up on the tools.scientiamobile.com website, since it is running the WURFL API in high-performance mode.

Cheers!

Hi Hannes,

We've recently released a newer version of the WURFl API (v1.5). Please upgrade to the newest release available and this mis-detection should go away.

Thanks and cheers!

Hi tntwurfl, You are correct in assuming that the "getDeviceForRequest(uagent)" method that you use in the Standalone WURFL Java API does not exist in the WURFL Cloud Java API. However, one way of getting around this is to craft a mock HTTP request with the User-Agent you want to resolve and pass it...

Hi,

The WURFL API 1.5 is available for download here.

Cheers!

Hi Chris,

Will do.

This issue only affects the WURFL Cloud. If you use our standalone WURFL API V1.5 or newer, you will not experience this issue.

Cheers!

Hi Chris,

We have identified the issue and we are working on an update to the WURFL Cloud to fix it. Thanks for the heads-up!

Cheers!

Hi Chris,

We will look into this issue. Could you also tell us what the fields stand for? Cheers!

Hi Chris, OK - so switched back to the cloud and it is displaying the mobile versions for IOS and Windows and BlackBerry. So I am officially going mad :oops: Glad to see that the issue has been resolved. Not sure why you do not just send back what is there to be uniform across all devices and if And...

Hi Chris, In that case, the issue is probably because of the reasons I mentioned in my post above. Could you please run these User-Agents on your end and let me know if you see the "mobile_browser_version" capability's results for them? Mozilla/5.0 (BlackBerry; U; BlackBerry 9800; en) AppleWebKit/53...

Hi Chris, Do you have a sample User-Agent set that will produce the result you see? FYI, not all device IDs will have the "mobile_browser_version" capability populated. A notable example is Android User-Agents where the stock browser app is typically updated via OS updates and "mobile_browser_versio...

Hi Chris,

Thanks for the detailed information. The issue was that the marketing name of this device wasn't populated in WURFL and hence was not displayed. I have corrected the issue and you should see the marketing name begin to appear when the WURFL Cloud data is next refreshed.

Thanks and cheers,