Hi Casey,

Sorry about that. We’ve recently done some work on upgrading our JSON parsing library and it looks like this issue will be fixed when we release 6.1.1. We don’t have an official release date yet, but I’ve made a note to send you an email when it’s released.