I was working with a subscription and the response came back with an error. Nothing checked for the error, so when a value was nil that shouldn't have been, my call returned a runtime error. That was difficult to track down. Perhaps this isn't different enough from #8 to warrant a new issue, but it's related. This is the line that is liberally catching the errors.