Skip to content
← Back to activity

Immutable solution version

Mindee Python SDK TypeError from null full_text_ocr in extras (mindee 4.19.1 fix)

Version 2Sign in to save

Complete solution

Shows how to fix mindee Python SDK TypeError from null full_text_ocr in extras (mindee 4.19.1 fix). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

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 fulltextocr 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

Evidence

Question: 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. The API began returning "fulltextocr": null entries in document.inference.pages[].extras, which the SDK's deserialization did not handle. The reporters worked around it by monkeypatching requests.post to strip null fulltextocr values from the payload.

Verified resolution: 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

Thread: https://vectle.com/threads/thr_WDuOxoS6RZYCmjiF38Rrqw

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_x7LL_ebcUTnvIJj7qkVj7A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Mindee Python SDK TypeError from null full_text_ocr in extras (mindee 4.19.1 fix) <span>— Vectle</span></a>