Hi,
I need a some help as I am getting some invalid browser information back from wurfl.
I have ran a query using my Samsung Galaxy Note 4 using the stock android browser with a user-agent string (Mozilla/5.0 (Linux; Android 5.1.1; SAMSUNG SM-N910F/N910FXXU1COI1 Build/LMY47X) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/2.1 Chrome/34.0.1847.76 Mobile Safari/537.36). Using the request to get device, the "advertised_browser" capability returns "Chrome" but it is not chrome.
is this a known bug or have you encountered it before?
Cheers,
Hafeez
Android Browser not correctly identified
Re: Android Browser not correctly identified
Hi Hafeez,
What version of the Java API are you currently using?
Aaron
What version of the Java API are you currently using?
Aaron
Re: Android Browser not correctly identified
Aaron,
I'm using GeneralWURFLEngine to get me the device for the userAgent i passed in and then from this device i get the "advertised_browser" capability.
I have looked up the userAgent by using http://dbapi.scientiamobile.com/explore/ and even according to this the browser is chrome mobile.
Regards,
Hafeez
I'm using GeneralWURFLEngine to get me the device for the userAgent i passed in and then from this device i get the "advertised_browser" capability.
I have looked up the userAgent by using http://dbapi.scientiamobile.com/explore/ and even according to this the browser is chrome mobile.
Regards,
Hafeez
Re: Android Browser not correctly identified
Hi Hafeez,
Thank you for providing that bit of information. The issue you are running into has been fixed since version 1.6.3.0, thus, if you are using a version prior to that, you will need to update in order to correctly identify the Android browser.
We release a new version every two months with improvements and fixes so I highly recommend updating when possible to take full advantage of the API.
Let me know if you have any other questions or concerns.
Aaron
Thank you for providing that bit of information. The issue you are running into has been fixed since version 1.6.3.0, thus, if you are using a version prior to that, you will need to update in order to correctly identify the Android browser.
We release a new version every two months with improvements and fixes so I highly recommend updating when possible to take full advantage of the API.
Let me know if you have any other questions or concerns.
Aaron
Last edited by aaronp on Mon Jan 25, 2016 11:13 am, edited 1 time in total.
Re: Android Browser not correctly identified
Aaron,
Sorry misunderstood your question, the Java API version is 1.5.3.1.
Am i using the latest version?
Regards,
Hafeez
Sorry misunderstood your question, the Java API version is 1.5.3.1.
Am i using the latest version?
Regards,
Hafeez
Re: Android Browser not correctly identified
Hafeez,
The latest Java API release is version 1.6.4.1 which can be found within your file manager.
Feel free to let me know if you run into any issues in updating your API.
Aaron
The latest Java API release is version 1.6.4.1 which can be found within your file manager.
Feel free to let me know if you run into any issues in updating your API.
Aaron
Who is online
Users browsing this forum: No registered users and 5 guests