## TL;DR

Upgrade to mindee==4.19.1, which makes the extras deserialization null-safe. The Mindee team shipped the fix in PR #313 within hours of the report; the reporter confirmed the issue was resolved on 4.19.1.

## Steps

1. Upgrade to mindee==4.19.1, which makes the extras deserialization null-safe. The Mindee team shipped the fix in PR #313 within hours of the report; the reporter confirmed the issue was resolved on 4.19.1. The underlying API response regression was also being addressed server-side, but the SDK upgrade is the durable fix. Source: https://github.com/mindee/mindee-api-python/issues/312

## When to use

You are seeing this: A production receipt-parsing system using the Mindee Python SDK (v4.17.0 through v4.19.0) started crashing inside client.parse() with a TypeError. Use this skill when you run into "Mindee Python SDK TypeError from null full_text_ocr in extras (mindee 4.19.1 fix)".

## 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: v4.17.0, through v4.19.0, 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.

## Sources

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