Thanks for the response. We haven't used the virtual ones before and will have to look in to that - are those available on the non-cloud version as well?

My customers are noting that sometimes we report down to the third number for the iOS version (e.g. device_os_version = 8.0.2) and other times we do not (e.g. 7.1.2 never shows, just 7.1). I have thus far responded that Apple doesn't always expose enough information for us to detect that difference,...

We were still on the Java API 1.4.4 - I've confirmed that upgrading to 1.5.0.1 will correctly resolve IE11.

Thanks again.

Ah, gotcha. I'll do some more testing with our version then and see if I just need to upgrade to the latest. Thanks.

It looks like IE11 is being used now - from what I can gather the IE11 for Windows 8.1 is already released and IE11 for Windows7 is not yet officially released but does have user agent string information out there. Here is some Microsoft documentation: http://msdn.microsoft.com/en-us/library/ie/hh86...

We're a licensed customer and have spoken in the past. With the new iPhones being announced as well as iOS 7 coming out soon - can you provide us just a general update as to if/when new attributes will appear in the wurfl.xml file with regards to either the new phones or OS? Let me know if you need ...

Sure - you guys should have my email address, let me know if not. How about you email me the contact information of who I should call (I'll probably call tomorrow, but possibly still today).

Do you guys have any further updates on this topic? My Product folks are asking generally the same question here about how we can have the WURFL data accurately reflect the iPhone5 users. Any updates or ideas would be appreciated. Thanks.

We are indeed using 'device_os' to make this distinction, but are using it as a more global 'iOS/Android/BlackBerry/WindowsPhone' reporting feature. In this case, we probably don't want to distinguish between the different OS since we're really recording the type of device. Regardless, thanks for th...

Yes, a virtual capability seems to be a good fit for this type of scenario. I'd just recommend that if that is the way it goes then support should be consistent for Chrome/IE/Firefox/etc. with that new virtual capability so that we can switch over to using that capability across the board (and don't...

Resurrecting this thread as it seems appropriate: Question: Why are Safari 525 and 530 the only browser 'version' available for desktop Safari? Those versions of webkit are very old at this point and since an actual version is not also supplied by WURFL (e.g. 5.1.7), it seems there is no way current...

Thanks for the quick response. This all makes sense and I'll update our definitions. It must have been a mistake on my part when searching the latest definition file that I didn't see the newer Firefox versions in there. I'll post back if they are indeed missing in my download, but I bet I overlooke...

What is your stance on keeping up with the latest versions of browsers? For example: Firefox 15 was released in August, and Firefox 16 was released in October, but the weekly snapshot has not been updated to specify either of those new versions. We're using the Java API (1.4.1), and while the browse...

Pretty self explanatory - this happens both from within my application with the latest WURFL definition file as well as on your home page where I can test the user agent string. I haven't tested an actual iPhone running iOS6 yet, but will do so soon... Update: An iPhone comes up as apple_iphone_ver6...

Email sent.

Configuration: Java API: wurfl-1.4.0.1.jar wurfl.xml version: 2012-04-29_wurfl.zip *Note: Recreated issue on local box with latest library and definitions as well (wurfl-1.4.0.3.jar and 2012-07-29_wurfl.zip) Issue: We've been seeing a lot of collection coming in as 'generic_web_crawler' where we th...

Go figure - I saw your message about not being able to re-create this problem and decided to deploy to our QA server to make sure it wasn't something strange on my box. It works fine in QA. I still can't figure out why this is happening locally, but I'm not going to spend more time on it right now u...

I did both simultaneously. I've had this on the back burner waiting for the official licensing, and now when I fired it up again this morning I got the latest code and wurfl.xml and found this in my initial testing.

Using the Java API 1.4.0.1.jar Configured with EngineTarget.accuracy (tried both programmatically as well as through wurfl-config.xml) Using the wurfl xml file from our customer account link dated 4/29/12 Firefox, Opera, Safari, IE all are detected as expected Problem: The current version of Chrome ...

Any new updates on this topic or a time frame when there may be?