We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the template js file created by html2js preprocessor contains some strange characters that caused the error: SyntaxError: Parse error.
For example, the error message: PhantomJS 1.9.8 (Mac OS X 0.0.0) SyntaxError: Parse error at http://localhost:9777/base/app/views/fido-header-reference.html.js?9ac748880914d633717d67a5ef14c1b66e6275cd:189
I looked into the file http://localhost:9777/base/app/views/fido-header-reference.html.js at line 189, .............')[1]==='viewInvoice'}">
\n' +
Please notice that strange characters 
 appears in it. I've verified multiple files with the same error, the same strange characters appears.
Please verify and verify.
Thanks. Frank
The text was updated successfully, but these errors were encountered:
@franksongca , had similar problem and in my case the utf-8 symbol was really present in the source html. So removing all such occurrences helped.
Sorry, something went wrong.
No branches or pull requests
the template js file created by html2js preprocessor contains some strange characters that caused the error: SyntaxError: Parse error.
For example, the error message:
PhantomJS 1.9.8 (Mac OS X 0.0.0)
SyntaxError: Parse error
at http://localhost:9777/base/app/views/fido-header-reference.html.js?9ac748880914d633717d67a5ef14c1b66e6275cd:189
I looked into the file http://localhost:9777/base/app/views/fido-header-reference.html.js at line 189,
.............')[1]==='viewInvoice'}">
\n' +
Please notice that strange characters 
 appears in it. I've verified multiple files with the same error, the same strange characters appears.
Please verify and verify.
Thanks.
Frank
The text was updated successfully, but these errors were encountered: