Hi Roey, The issue is two fold. Android 4.4 was never shipped to the Samsung Galaxy Nexus, as you can see here (the standard Galaxy Nexus' codename is maguro). As you mentioned the device is probably running a ROM with Android 4.4, which is why a positive detection was not made. We will add this Use...

Hi Pravesh,

The WURFL API 1.5.1 has been released!

Cheers!

Hi Ashish, WURFL will tell you (via the xhtml_preferred_charset capability) if a specific device supports UTF-8 encoding. However, we do not currently have a capability to check if a device supports a specific UTF-8 script(like Hebrew or Indic) or not. However, we are constantly on the lookout for n...

Hi,

Thanks for the heads-up! The device has been added to WURFL and should be available in the next WURFL.xml weekly snapshot onwards.

Cheers!

Hi there! Can you provide us with the User-Agent string for this device so we can look into this issue?

Cheers!

Hi Maurizio,

The User-Agent has been added and should be in the next WURFL.xml snapshot onwards.

Cheers!

Hi Charis,

The recently introduced "is_app" virtual capability is what you are looking for.

Cheers!

Hi Maurizio,

The device has been added and will be present in the next WURFL.xml snapshot onwards.

Cheers!

Hi Ashish, A browser's support for UTF-8 encoding does not automatically mean that the browser supports all UTF charsets. We quickly ran a test with a Lumia 800 that we had laying around. It did successfully display most UTF-8 encoded charsets like Hebrew, Arabic and Cyrillic, it did fail to render ...

Hi Pravesh, I think I was a bit unclear in my previous post. All WURFL APIs v1.5 onwards support MSIE 11 detection with the standard capabilities(mobile_browser, mobile_browser_version etc.) as you can see here . Although the capability name does say "mobile", it will work for desktop browsers as we...

Hi there,

It looks like the UAs are taken from the device emulator in the Android SDK, rather than the device itself. For reference, the Nexus One's UA looks like this and the Xoom's UA like this.

Cheers and thanks,

Hi Pravesh,

We've added support for MSIE 11 related virtual capabilities in the next WURFL API update (v1.5.1). Please stay tuned for news about the release of the v1.5.1 update.

Thanks and cheers!

Hi Renato,

The standalone WURFL API v1.5.1 is slated to be released early next month. We will then roll the API update to the WURFL Cloud. We will definitely keep you in the loop regarding this.

Thanks and cheers!

Hi Gaurav, We do send out a quarterly newsletter to everyone with a Scientiamobile.com account, which contains information about new WURFL API releases, along with other updates. Our most recent newsletter was sent out on December 12 2013. If you did not receive that, please email us at cr (at) scie...

Hi Gaurav,

The WURFL API v1.4.2 is more than a year old. Please use a newer version of the WURFL API for optimal detection. Here is a link to the WURFL Java API v1.5.0.1.

Thanks and cheers!

Awesome! Thank you for using WURFL. Now that you are a licensed customer, you should also be able to access our enterprise support system . This system will link your account information to your question so that our support personnel have access to all the relevant information to answer your questio...

Hi Chris,

Virtual capabilities are retrieved by "getVirtualCapability" and not via "getCapability". Here's the documentation for that method in the WURFL PHP API.

Cheers!

Hi, Has this been pushed to the cloud? Not yet. We will keep you updated, as promised, when the WURFL Cloud is updated. I got a newsletter about new Virtual Capabilities in API 1.5 and thought the IE11 fix was rolled out on the cloud too. We made a blogpost a while ago about the Virtual Capabilities...

Hi there,

The advertised_* capabilities are virtual capabilities and they are not linked to the WURFL.xml snapshots. They are instead computed by the WURFL API on the fly and as such are not enumerable like the standard capabilities are.

Cheers!

Hi Gaurav,

Thank you for your post. To help us look into this issue and replicate it on our end, what language and version of the WURFL API are you on and what date of the wurfl.xml file is it using?

Cheers!