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

Hi Fadi,

Due to private information, I have sent you an email regarding your ImageEngine account.

Thanks,

Aaron

Hi Paul! It appears that you are indeed using an outdated `wurfl.xml` which is incompatible with API v1.8.0.1 You will need to redirect your path to: public const String WurflDataFilePath = "~/App_Data/wurfl.zip"; This default data file path contains an evaluation `wurfl.xml` compatible with v1.8.0....

Michael,

API v1.8.0.1 has been published to NuGet (https://www.nuget.org/packages/WURFL_Official_API) and the .dll files are production ready. Let me know if you have any other questions or concerns.

Thanks,

Aaron

Hi Michael, It appears that the issue is occurring due to an error during the obfuscation phase of the .dll I have uploaded an updated version of the API (v1.8.0.1) addressing this issue to your File Manager (first login to your ScientiaMobile account, then 'My Account' -> 'File Management' -> 'Prod...

Hi Michael,

I noticed that your last WURFL snapshot update occurred on the 29th of June. Are you able to update your `wurfl.zip` to the latest release and try running WURFL again?

Look forward to hearing back.

Thanks,

Aaron

Hi David, Are you able to provide your project source code? In order for us to determine that WURFL is being used correctly, we must measure it on our end to verify that the memory is going up to 500 MB. Also, you may be interested in looking into our InFuze IIS API (http://scientiamobile.com/page/w...

Hi Quint,

We were unable to find any issues dealing with iOS 9.3.3 However, we are currently working to resolve some issues, similar to what you are seeing, for iOS 10. If you have any details or information for the iPhone SE in question, please do not hesitate to let us know.

Thanks,

Aaron

Per our email conversation: We have made updates to the API (v1.7.1.1) so that only one static instance of List<string> is instantiated (during engine startup), as opposed to an instance per each request. While the List is still in LOH (given the size), the garbage collector will never remove it. In...

Hi Kemar,

Thank you for providing the information. Are you able to confirm which version of Tera-WURFL (DB API) you are currently using?

Thanks,

Aaron

Hi Kemar, In order to reload WURFL data, you must first login to your ScientiaMobile account and then go to: 'My Account' -> 'View Account' (under license) -> https://data.scientiamobile.com/xxxxx/wurfl.zip An alternate, and recommended, method would be to automate your download. The following link ...

Hi Irakli,

Can you confirm your API version as well as the date of your `wurfl.xml`? Also, are you able to provide the user agent string of the device for which you are hitting your web page with?

Thanks,

Aaron

Hi Vivek,

Given the nature of your issue, we are unable to troubleshoot your application as it does not belong to us. However, do feel free to provide any user agent strings which are not being resolved properly.

Thanks,

Aaron

Hi Stephen,

To clarify, you can use the latest `wurfl.xml` with an older API; however, while the `wurfl.xml` is backwards compatible with the API, the inverse is not always true.

Hope this cleared things up for you. Let me know if you have any further questions.

Thanks!

Aaron

Hi Luke, The capability you will want to refer to is the `advertised_browser_version` as it reflects an accurate portrayal of the browser version. The `mobile_browser_version` capability for this device ID is set at 30. However, when the detection occurs, the advertised virtual capabilities will run...

Hi, The difference between the virtual capabilities and regular capabilities in WURFL is that the virtual capabilities are calculated through the WURFL API usually by combining physical capabilities defined in the wurfl.xml. In the case of the virtual capability is-smartphone, we take into considera...

Hi, The significance in the "DO_NOT_MATCH" string is that we do not want any user agents that you encounter to match these devices. The reason for this can vary, but in the case of Apple devices, it is for a very specific reason. This reason is that Apple devices in general have very generic user ag...

Hi Rath, Thank you for providing the information. I was able to replicate your error and conclude that because the 2016-06-12 `wurfl.xml` has some new devices added to it that are not handled properly in the version of the API that you are running (v1.5.0.1), you will need to update to our latest AP...

Hi Sunny, Thank you for letting us know. Are you able to provide us with some sample UAs that are displaying this behavior as well as a stack trace or any code samples showing how you are running your detection? Also, if possible, I would highly recommend updating your API to version 1.7.1.0 as we h...

Hi Quint,

Thank you for letting us know. I have notified my engineering team about this behavior and will follow up with you as soon as I receive an update. In the meantime, are you able to let me know which OS version the iPhone SE was running?

Thanks,

Aaron