Skip to content
New issue

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

parseXmlResponse Error and Error handling #43

Open
SebastianMetzger opened this issue Apr 18, 2016 · 3 comments
Open

parseXmlResponse Error and Error handling #43

SebastianMetzger opened this issue Apr 18, 2016 · 3 comments

Comments

@SebastianMetzger
Copy link

It is pretty cool, that abbyy provides a NodeJS library for their API and so far it also worked well for us!

We currently have issues, that the processImage task is not working for certain users and the error handling of the ocrsdk.js is a bit buggy itself, as the error message is show as [Object object].
So it is hard to debug right now, without monkey patching the library.

Probably there is a missing "toString()" after message or something?
taskDataCallback(new Error(response.error.message), null);

Here is the example from our log file:
abbyy error

@Dmitry-Me
Copy link
Contributor

No, not toString(). This fa44845

@Dmitry-Me
Copy link
Contributor

@SebastianMetzger Could you please try the changes from fa44845 ?

@SebastianMetzger
Copy link
Author

thx, for providing the fix.

I build in my own error logging and did not try yours yet.
Just upgraded it and will report, if it worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants