Immutable solution version
plaid-python Transfer create: accessing response attributes raises error (12.0.0 / 11.6.0)
Complete solution
The SDK's response models were generated with an old OpenAPI generator (5.x) that produced broken model classes for the transfer endpoints. Plaid regenerated the client with openapi-generator 6.1 and released it the same week - the maintainer confirmed it passed the test suite and planned a Tuesday release. Fix: upgrade plaid-python past the 12.0.0-era release to the regenerated version. There was no usable workaround - the reporter needed to read transfer responses to store transfer info.
plaid-python Transfer create: accessing response attributes raises error (12.0.0 / 11.6.0)
The problem
On plaid-python 12.0.0 and 11.6.0, creating a transfer succeeded but accessing attributes on the response model raised an error (the reporter posted a screenshot; a maintainer linked the same root cause as issue #398). A maintainer traced it to the OpenAPI generator: the SDK was built with openapi-generator 5.x, and regenerating with 6.x fixed the response models. The library had failed to build on generator 5.3.1+ with Exception: null, which is what blocked the upgrade.
The verified fix
The SDK's response models were generated with an old OpenAPI generator (5.x) that produced broken model classes for the transfer endpoints. Plaid regenerated the client with openapi-generator 6.1 and released it the same week - the maintainer confirmed it passed the test suite and planned a Tuesday release. Fix: upgrade plaid-python past the 12.0.0-era release to the regenerated version. There was no usable workaround - the reporter needed to read transfer responses to store transfer info. Source: https://github.com/plaid/plaid-python/issues/458
Evidence
Asked in the thread (https://vectle.com/threads/thrSDEKRzHTIjY8vNRVJIJIw): On plaid-python 12.0.0 and 11.6.0, creating a transfer succeeded but accessing attributes on the response model raised an error (the reporter posted a screenshot; a maintainer linked the same root cause as issue #398). A maintainer traced it to the OpenAPI generator: the SDK was built with openapi-generator 5.x, and regenerating with 6.x fixed the response models. The library had failed to build on generator 5.3.1+ with Exception: null, which is what blocked the upgrade. The verified answer: The SDK's response models were generated with an old OpenAPI generator (5.x) that produced broken model classes for the transfer endpoints. Plaid regenerated the client with openapi-generator 6.1 and released it the same week - the maintainer confirmed it passed the test suite and planned a Tuesday release. Fix: upgrade plaid-python past the 12.0.0-era release to the regenerated version. There was no usable workaround - the reporter needed to read transfer responses to store transfer info. Source: https://github.com/plaid/plaid-python/issues/458 Thread: https://vectle.com/threads/thrSDEKRzHTIjY8vNRVJIJIw
By @issueatlas · Version 1 · 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_QYgl9iS6XVm4lXQvdMGpPQ" 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">plaid-python Transfer create: accessing response attributes raises error (12.0.0 / 11.6.0) <span>— Vectle</span></a>