Hi Siddharth, I've spoken with my mobile data team and can confirm to you that the Edge 14 browser will be detected in the next API release. Also, do note that, unless there was a typo, the second user agent string appears to be invalid as the "m" in "mozilla" needs to be capitalized. Let me know if...

Hi Bernard,

Thanks for filling us in. I believe that is all the information we need at the moment and will relay it to my engineering team. I will provide you with an update once the TTL is adjusted.

Regards,

Aaron

Bernard,

Thank you for the decreased TTL request. Are you able to let us know if a 12 month TTL on the WURFL.js cookies is within bounds for France and the UK?

Regards,

Aaron

Hi Bernard,

Thank you for letting us know. The TTL can only be reduced through the code; however, we are looking into adjusting the TTL and will surely follow up with you as soon as possible.

Regards,

Aaron

Hi Medicom,

That's correct - once our data is updated the changes will be reflected in WURFL.

Aaron

Hi Medicom, The difference in values is as intended and the capability which you will want to reference in this case is advertised_device_os_version. This is because advertised capabilities are pulled directly from the user agent string during detection (in this case: OS 10_1), whereas the unadverti...

Hi!

I can confirm that the email is indeed support@scientiamobile.com

Look forward to hearing from you soon.

Regards,

Aaron

Hi John, The reason why the device model for the previously mentioned user agent string Mozilla/5.0 (iPhone; CPU iPhone OS 9_0_2 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Mobile/13A452 [FBAN/FBIOS;FBAV/40.0.0.42.290;FBBV/15252421;FBDV/iPhone7,2;FBMD/iPhone;FBSN/iPhone OS;FBSV/9.0.2;FBS...

Hi Jaroslaw, Thanks for the information. We have found the source of the issue and deployed the fix to production. All services are now returning the expected values. Note that your local WURFL Cloud Client cache will still have the incorrect values cached, so you although no client update is requir...

ScientiaMobile has released version 1.8.1 of its WURFL API. To get the best possible performance from your WURFL solution, you should have both the latest API (1.8.1) and our most recent XML (released weekly to Commercial license customers). What’s New in WURFL Release 1.8.1 - Added support for Andr...

Hi Ofer!

Please feel free to send the file and any further detail over to support@scientiamobile.com and we will take a deeper look.

Thanks,

Aaron

Hi Marc,

I see what you are saying and will notify my mobile data team to get the user agent's model updated.

Thanks,

Aaron

Hi Marc! If the `model_name` capability is what you are referring to, the return value is intended to be `Z955L`. The model name will not include the brand as well. However, if you are looking for both the brand and model name (ex. Samsung Galaxy S5), you will want to use the `complete_device_name` ...

Hi Marc,

Thanks for the update! This user agent has been in our database and, if you are unable to properly detect it, you may want to try updating your WURFL Snapshot.

Aaron

Hi Marc,

The user agent is still invalid as "BUILD" should not be capitalized.

Aaron

Hi Ofer, Thank you for providing the stack trace. We are looking into the issue and will follow up with you as we learn more. In the meantime, are you able to check if you have a whitespace in front of the XML declaration? The `Caused by: org.xml.sax.SAXParseException: Content is not allowed in prol...

Hi Marc, The ZTE user agents have been updated in our database. In order to see the changes, you will need to update your `wurfl.xml` file. You can find the link for the update by logging into your organization's primary licensed account, then go to: 'My Account' -> 'View Account' for WURFL InFuze f...

Hi Marc,

Thank you for letting us know. We have updated the model number in our database and the changes will be reflected in the next Snapshot release.

Feel free to let us know if you have any other questions or concerns.

Thanks,

Aaron

Hi Stephen, Thank you for letting us know. The change from [string,string] to [any,any] appear to have been made in order to meet compliance with the release of Scala 2.12-M4. I will discuss this with the engineers who worked on this project and will follow up with you when I have a more in-depth an...

Hi Raju, We appreciate your desire to contribute, however, we are currently not accepting external code/documentation/API comments. If anything changes in the near future, I will surely let you know. Also, the following link is a guide for the OnSite Scala API. Let me know if you have any other ques...