Closed kevinrook closed 5 years ago
It looks like this was triggered by a network error (502 or any error that does not include an array of errors in the response). I will update the error handling so it will display a more useful message (can't do much about the 502 itself)
I have updated error handling in version 3.2.3
I've started getting the below errors