Closed wh1t3cAt1k closed 1 year ago
On a side note, can the error be made more specific so we can catch it properly?
"Unexpected token <" is too cryptic, I thought that there was something wrong with our manifest; I'd expect a more descriptive error message about the validation service not being accessible.
I'm assuming that the browser attempt was because the cli didn't work. Note: it's not expected to work by itself because it's an API that needs a POST with the manifest in the body.
Based on the call stack for the syntax error, it appears that the response provided was not an expected json response. This could be improved to have a better message for the developers in cases where the response isn't json (which is what the validator returns), but didn't have a problem sending the post.
I'm guessing it's working now though (I don't get the 502 myself).
Add a bug to our backlog to fix the error message.
Update package published now.
https://validationgateway.omex.office.net/package/api/check?clientId=Default