Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Using the SDK method files.upload with a file stream and a purpose value (e.g. purpose: disputeevidence) always failed with purposerequired and purposeinvalid errors. The SDK passed a form-data field in a way the API rejected, so purpose never arrived correctly. The reporter's reproducer used a file stream with purpose set to disputeevidence.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Confirmed as an SDK bug and fixed in checkout-sdk-node 3.3.0; upgrade to 3.3.0 or newer. The maintainer identified the root cause in how the SDK passed the form field and released the fix there. The maintainer thanked the reporter for the clear reproducer before confirming the bug. Source: https://github.com/checkout/checkout-sdk-node/issues/418
Source: https://github.com/checkout/checkout-sdk-node/issues/418
Shows how to fix files.upload fails with purpose_required / purpose_invalid (fixed in 3.3.0). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix checkout.com files.upload fails with purpose_required: broken form-data handling, fixed in 3.3.0. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix files.upload purpose ocr fails type checking - fixed in mistralai 1.5.2. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.