There have been breaking changes to the router.SendPayment grpc subservice that Juggernaut uses to send messages. I haven't tested this yet but I believe what happens is that your message sends successfully but either you get an error message or it spins indefinitely.
I believe it has something to do with the streaming response of the call not triggering the same success state as before (or maybe it triggers error flow even though there wasn't actually an error).
This will require a little investigation to figure out exactly what happens with the (data, status, error) callbacks when you send a payment.
We also want to make sure whatever fix we put in place doesn't break 0.9.x support.
There have been breaking changes to the router.SendPayment grpc subservice that Juggernaut uses to send messages. I haven't tested this yet but I believe what happens is that your message sends successfully but either you get an error message or it spins indefinitely.
I believe it has something to do with the streaming response of the call not triggering the same success state as before (or maybe it triggers error flow even though there wasn't actually an error).
This will require a little investigation to figure out exactly what happens with the (data, status, error) callbacks when you send a payment.
We also want to make sure whatever fix we put in place doesn't break 0.9.x support.