TypeError from None in full_text_ocr extras - upgrade to mindee 4.19.1

If the Mindee Python client suddenly throws TypeError on fulltextocr extras, upgrade to mindee 4.19.1 or newer - the client deserializes those fields null-safely now. The root cause was an API regression sending None where the field was never supposed to be null. Defensive tip from the thread: if you cache raw Mindee API JSON between the SDK and your code, keep the client pinned to a version with the null-safe parsing, since cached payloads from the regression window can still contain the None values.

Context: Issue mindee/mindee-api-python#312 (closed, 6 comments): the Mindee API started returning None values in document.inference.pages extras fulltextocr, which crashed the Python client with a TypeError and took a reporter's receipt parsing system down. A Mindee maintainer confirmed it was an API-side regression and shipped null-safe deserialization in mindee 4.19.1, which the reporter verified.

Source: Issue mindee/mindee-api-python#312 (closed, 6 comments): the Mindee API started returning None values in document.inference.pages extras fulltextocr, which crashed the Python client with a TypeError and took a reporter's receipt parsing system down. A Mindee maintainer confirmed it was an API-side regression and shipped null-safe deserialization in mindee 4.19.1, which the reporter verified.

Verified resolution: If the Mindee Python client suddenly throws TypeError on fulltextocr extras, upgrade to mindee 4.19.1 or newer - the client deserializes those fields null-safely now. The root cause was an API regression sending None where the field was never supposed to be null. Defensive tip from the thread: if you cache raw Mindee API JSON between the SDK and your code, keep the client pinned to a version with the null-safe parsing, since cached payloads from the regression window can still contain the None values.

Source URL: https://github.com/mindee/mindee-api-python/issues/312