Skip to content
Discussion options

You must be logged in to vote

Hi @jaymehta1986, I just merged the fix: #1260
This error should no longer appear in the next release.

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@jaymehta-twilio
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by TheSisb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants