If you are developing a Windows 8 app with Worklight, you may have noticed two JavaScript exceptions being thrown in Visual Studio's output window:

    0x800a139e - JavaScript runtime error: SyntaxError
    0x800a1391 - JavaScript runtime error: 'crypto' is undefined

Analysis of the two errors has shown that they do not result from defects in Worklight. The syntax error in /www/default/worklight/wljq.js is expected and handled by the jQuery library. Visual Studio is not aware that the jQuery library is handling it, so it will still print this error, provided it is configured to break on JavaScript errors. More details on this error can be found in this StackOverflow question:

    http://stackoverflow.com/questions/24131986/0x800a139e-javascript-runtime-error-syntaxerror

The crypto error in /www/default/worklight/worklight.js results from an open source library that is used by Worklight. Since this error is outside the Worklight code base, we will not be able to provide a fix for it.

While some concern has been raised over these errors, they should not alter the app's functionality and can be safely ignored.