Page 1 of 1

Chrome detected as 'Generic web browser' using Java API

Posted: Wed May 02, 2012 10:59 am
by elrichar
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 is detected as 'Generic web browser'
The user agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.168 Safari/535.19

Re: Chrome detected as 'Generic web browser' using Java API

Posted: Wed May 02, 2012 11:34 am
by kamermans
Thanks for the message, we are looking into this now. In the meantime, do you know if this started when you updated the data, or the API?

Re: Chrome detected as 'Generic web browser' using Java API

Posted: Wed May 02, 2012 11:54 am
by elrichar
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.

Re: Chrome detected as 'Generic web browser' using Java API

Posted: Wed May 02, 2012 12:06 pm
by kamermans
Ok, we'll get to the bottom of it and get back to you ASAP.

Re: Chrome detected as 'Generic web browser' using Java API

Posted: Thu May 03, 2012 2:26 pm
by luca.passani
elrichar wrote: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.
The engineering team could not reproduce the problem.

Can you please send me an email at luca @ scientiamobile[...]. I will put you directly in contact with one of the Java engineers to get to the end of this.

Thank you

Luca

Re: Chrome detected as 'Generic web browser' using Java API

Posted: Thu May 03, 2012 3:30 pm
by elrichar
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 unless it happens in subsequent environments. Thanks for the quick follow up.