"WrongResponse" AGAIN
@Jean-Yves Sireau @Raunak @Kaveh Guys, this whole “Wrong Response”-error issue is getting out of control. It went from an occasional annoyance to a regular phenomenon and is now at a stage where it’s actually rendering my application useless. What’s worse is that it was originally only limited to “Proposal”-requests:
{
"echo_req": {
"symbol": "R_50",
"subscribe": "1",
"duration": "120",
"currency": "USD",
"amount": "100",
"proposal": "1",
"basis": "stake",
"duration_unit": "s",
"contract_type": "CALL"
},
"error": {
"message": "Sorry, an error occurred while processing your request.",
"code": "WrongResponse"
},
"msg_type": "send_ask"
}
but now crops up with “Balance”-
{
"echo_req": {
"balance": "1"
},
"error": {
"message": "Sorry, an error occurred while processing your request.",
"code": "WrongResponse"
},
"msg_type": "balance"
}
“Authorise”-
{
"echo_req": {
"authorize": "<removed>"
},
"error": {
"message": "Sorry, an error occurred while processing your request.",
"code": "WrongResponse"
},
"msg_type": "authorize"
}
“Ticks_History”-
{
"echo_req": {
"granularity": 120,
"count": "40",
"ticks_history": "R_50",
"subscribe": "1",
"style": "candles",
"end": "latest"
},
"error": {
"message": "Sorry, an error occurred while processing your request.",
"code": "WrongResponse"
},
"msg_type": "ticks_history"
}
and even “Candles”-requests:
{
"echo_req": {
"granularity": 120,
"count": "40",
"ticks_history": "R_50",
"subscribe": "1",
"style": "candles",
"end": "latest"
},
"error": {
"message": "Sorry, an error occurred while processing your request.",
"code": "WrongResponse"
},
"msg_type": "ticks_history"
}
Whatever changes were made recently, please roll them back. Things are seriously broken. I'll raise a ticket at Github as well.
Comments
Got feedback via Github (https://github.com/binary-com/websockets/issues/55) - apparently the spate of errors is due to system maintenance.