You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally, the response body is missing the expected 'FieldName' in the file 'webclient/gen/api_client.py' at line 123. This issue occurs right at the beginning when the request is made, before any attempt is made to read the response body. The code likely requires a try-catch statement to handle the missing field gracefully. It's also worth considering whether 'FieldName' should always be present in the response.
I tested adding a try-catch block around the code, and the error stopped occurring. I also added a print statement to log the absence of 'FieldName' when it is missing.
Reponse body:
The text was updated successfully, but these errors were encountered:
Hi @JaffeMarques. Unfortunately, I wasn't able to reproduce described behavior on DocumentReader version 7.4. Could you please provide more information, like:
Document type (passport, ID card, etc.) and scenario (Ocr, Full_process, etc.)
Your library version and server (SDK) version if you are using non-public API
Error persistency (Is it persistent error or it can appear at times)?
Parameters for ProcessParams. It would be cool if you can provide a piece of code.
Have you ever get such error with any other documents?
Occasionally, the response body is missing the expected 'FieldName' in the file 'webclient/gen/api_client.py' at line 123. This issue occurs right at the beginning when the request is made, before any attempt is made to read the response body. The code likely requires a try-catch statement to handle the missing field gracefully. It's also worth considering whether 'FieldName' should always be present in the response.
I tested adding a try-catch block around the code, and the error stopped occurring. I also added a print statement to log the absence of 'FieldName' when it is missing.
Reponse body:
The text was updated successfully, but these errors were encountered: