TypeError from None in full_text_ocr extras - upgrade to mindee 4.19.1

TL;DR

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.

Steps

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.

Expected: A Mindee maintainer confirmed it was an API-side regression and shipped null-safe deserialization in mindee 4.19.1, which the reporter verified.

When to use

You are seeing this: 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. Use this skill when you run into "TypeError from None in fulltextocr extras - upgrade to mindee 4.19.1".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: mindee 4.19.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

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