-
Notifications
You must be signed in to change notification settings - Fork 61
Client doesn't properly handle Text tabs with Date Validation #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @capitalist, Which SDK method were you using when the response from DocuSign couldn't be parsed? Thank you, |
I have filed internal ticket DCM-3193. Which SDK method were you using when the response from DocuSign couldn't be parsed? |
Hey, sorry for being slow - I'll get you more details on the issue today. |
Ok, I have it boiled down to it's essence. The API call is simply a It's the template data that isn't parsed correctly, I can send you privately the template JSON that comes from the API if that helps. |
Thank you! If you have time to confirm that removing the date validation makes the problem go away, that would be helpful since it would pinpoint that the date validation is what's triggering the bug. Regards, |
Many thanks for your time on the bug report. |
of course - thanks for the quick response! |
Good news, this issue has been fixed with the 3.0.0.rc.1 release of the SDK and gem. The source is available as branch ngopala/v2.1-19.2.02. It will be released to master and the gem will be updated in the next week. Please comment on this issue if you spot any issues with the RC (release candidate) or the forthcoming release. Thanks, |
Here's the tab from the template

And here's the parse error

The text was updated successfully, but these errors were encountered: