Hi JD We use a tool called SiteConfidence to monitor our sites. This is a desktop emulator and should be classified as desktop and not a wireless device. This was the case until recently when we upgraded our code to use API 1.4.0.3 and the latest database file. Unfortunately now the user agent is no...

Jan.Sobota@bsc-ideas.com wrote:This is for the sake of testing.

Unfortunately, Opera makes it really hard for WURFL (and for everyine else) to detect the host device. Anyway, I recommend that you check back in a few months. We may be able to introduce some nice new feature in the meantime

Hey J D, unfortunately Google has very light-heartedly decided from one day to the next the the Mobile Chrome UA string should also contain "Chrome" (previously it did not). The good news is that we fixed this right away with a maintenance release of the APIs (1.4.0.3 for Java) to address this issue...

I'm using wurflk 1.01 API, because we are using maven and because it was like that when I got the project(too much work to upgrade for no significant gain for the moment) For obvious reasons, ScientiaMobile does not support WURFL versions released before the creation of the company, or, equivalentl...

You think the user agent as an ID, I don't. My IDs are : Tac code (from GSMA) (when discussing with a device) a combination of brand and model names.(actually one of the most used datas) the user agent is just a characteristic, not much for our database. the problem is that I would like to get : - ...

PS : I still found strange that wurfl doesn't store all 8 Apple devices... for this kind of brands, you make whatever is need to comply with their ideas. they are too famous to not be in the file. We could add dummy profiles for all the devices, but how would we (or anyone for that matter) associat...

Bonjour Pierre If the only need of wurfl was to associate user agent and device, you would be right. But Wurfl is also a way from a device name to know all capacities of this device. For exemple in orange, we have multiple way to identify the device, and the user agent is not the only one, neither t...

OK. We will start planning for an has_physical_keyboard property in the future. Cannot commit to a precise date yet. Sometime Q4 seems reasonable.

miltonbenavides wrote:If I will update the new API (1.4.0.1) and with the file wurlf.xml (ver 2.3.2) I will can recognize the IPAD 3 without problems?

yes, you will be able to.

Jar version: wurfl-1.0.1-rc2.jar WURLF XML Version: 2.3.2 (Updated 02-07-2012) downloaded yesterday from http://wurfl.sourceforge.net/wurfl_download.php it looks like you guys are a few geological eras behind in terms of API. I suggest you upgrade to the latest (1.4.0.1). In fact, if you wait a few...

We checked and the UA string you provided matches apple_ipad_ver1_sub51. The capability is_wireless_device is true.

Can you please be more precise about your environment? API, wurfl.xml versions, etc.

Thanks

this is a known issue with the iOS. Apple has chosen to hide any information about the underlying device in the HTTP request. This is not a WURFL issue, it is an issue with any framework or even manual analysis of an HTTP request. You should complain to Apple for this. We chose to add conservative v...

end of summer. But there are quite a few things we want to get right, so there may be delays

You must be on a very old version of the API. We strongly suggest that you upgrade to the latest one (1.4). Support is one side of it, but the other is that you are missing on over one year updates in enhanced matching heuristics (covering iOS, Android and Windows Phone, among others) We will assist...

we are not observing the behavior you describe: http://tools.scientiamobile.com/?user-agent-string=Mozilla%2F5.0+%28Macintosh%3B+U%3B+Intel+Mac+OS+X+10.6%3B+fr%3B+rv%3A1.9.2.28%29+Gecko%2F20120306+Firefox%2F3.6.28 Can you please provide exact spec of the WURFL API (version and platform) and WURFL re...

We have no evidence that this is something different from a Kindle Fire at the moment, even though it might be. Amazon has certainly made an aggressive move against content providers with the introduction of such ambiguous/generic UA strings. As soon as the issue is clarified, we will do whatever we...

We recently did some updates to the repository to better recognize the Google bot. While it is not our intention to add full bot/crawler recognition to WURFL (it would be a red-herring, you cannot really tell a bot from the UA string), we are making an exception for obvious Google entries. Commercia...

is_tablet *is* a capability, so you are using WURFL for capability detection. The utility functions you mention are for the API own internal use. You shouldn't use those functions anymore that you would walk into a door that says 'staff only' only because you happen to see that it is not locked. Any...

Hey Preston, something isn't right. You shouldn't be using isDesktop and IsDesktopHeavyDutyAnalysis at all. In fact, thank you for pointing out, we will make that method private in future releases. That function, does not do what you think it does. You are only supposed to look at the capabilities t...

Hi Pilroy,

what we call the WURFL-DB does not implement any of the standard API. Can you please tell us more about what you are seeing where?

Thanks