plaid-python Transfer create: accessing response attributes raises error (12.0.0 / 11.6.0)

TL;DR

For "Exception: null": 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).

Exception: null

Steps

1. 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.
2. 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

Expected: 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.

When to use

You are seeing this: The SDK's response models were generated with an old OpenAPI generator (5.x) that produced broken model classes for the transfer endpoints. Use this skill when you run into "plaid-python Transfer create: accessing response attributes raises error (12.0.0 / 11.6.0)".

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: plaid-python 12.0.0, 11.6.0, generator 5.3.1, 12.0.0-era. If you are on something much newer or older, the details may have shifted.

Why this happens

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).

Sources

• https://github.com/plaid/plaid-python/issues/458

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