Chrome Browser not correctly identified

Are you absolutely, positively sure that your question does not fit anywhere else?
Posts: 4
Joined: Fri Jan 22, 2016 9:24 am

Chrome Browser not correctly identified

Postby hafeezM » Thu Oct 13, 2016 4:31 am


We are getting invalid browser information back from a customer device, the user-agent string (Mozilla/5.0 (Linux; Android 4.4.2; GT-N7100 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/ Mobile Safari/537.36) used in the request to get device, shows "advertised_browser" capability as "Chromium" but it should be chrome.

We are using wurfl version but i have tried updating to wurfl version but still returns chromium as browser used. I have looked up the userAgent using and according to this the browser is correctly identified as chrome mobile.

Is this a known issue?


Posts: 39
Joined: Mon May 30, 2016 4:59 am

Re: Chrome Browser not correctly identified

Postby amark » Thu Oct 13, 2016 9:34 am

Hi Hafeez,

The following user-agent string is being reported correctly as chromium for the "advertised_browser" capability. For information about how chromium based webview user-agent strings are formatted you can refer to this page from google. Virtual capabilities such as "advertised_browser" add an extra set of logic that parse the user-agent and will return the browser that it is advertising to be, whereas the "mobile_browser" capability will return the value as it exists in WURFL which is why you see "chrome mobile" on I hope this information has proved useful and if you have any more questions I will be happy to answer them.



Who is online

Users browsing this forum: No registered users and 1 guest