We are using the official C# wrapper for Dwolla’s API here:
We wanted to know if using version 5.4.0 should be sufficient to handle Dwolla’s upcoming changes involving HTTP/2.
We tried to upgrade to the latest stable version (6.0.0) but found that this version apparently reintroduced this bug, which is breaking our code:
Ideally this bug could be fixed, but until then, we just want to know if it’s okay to keep using 5.4.0 for the purposes of Dwolla’s HTTP/2 changes in December.
Hi @jacob-ez,
Thank you for reaching out with your concern about Dwolla’s upcoming changes involving HTTP/2 and the use of SDK version 5.4.0.
Regarding HTTP/2 Changes and Version 5.4.0: Based on our review, version 5.4.0 of the C# SDK should be sufficient to handle the upcoming HTTP/2 changes. Specifically, the SDK relies on HttpClient for managing headers, which inherently treats headers in a case-insensitive manner. This means that the “location” header being returned in lowercase should not cause any issues with the functionality of version 5.4.0.
Regarding the Bug in Version 6.0.0: We are aware of the deserialization issue you’ve mentioned in version 6.0.0. While this bug is under investigation and will be addressed in future updates, you can continue using version 5.4.0 for now without concerns related to the HTTP/2 changes.
Please feel free to reach out if you have any further questions or concerns!
This topic was automatically closed after 365 days. New replies are no longer allowed.