Hey, so this is pretty minor. Some of the logs that are showing on track js (the Unexpected token ones) are down to the api not returning a parseable json body when the response is an error (e.g. 401). This could be resolved if the body of the response (even if it's a error) is still json.
Hey, so this is pretty minor. Some of the logs that are showing on track js (the Unexpected token ones) are down to the api not returning a parseable json body when the response is an error (e.g. 401). This could be resolved if the body of the response (even if it's a error) is still json.
Culprits:
I'll update if I find others.