1351 has solved the problem with waiting 10-30s when blockStream error occurred. That specific error was false positive most of the time so almost immediate retry improved the UX significantly.
There is another error I see pretty frequently and that is getInfo API. This ticket might be about treat getInfo the same way as blockStream but we should consider any networking/lightwalletd errors to fall into the same bucket and generalize the solution.
1351 has solved the problem with waiting 10-30s when
blockStreamerror occurred. That specific error was false positive most of the time so almost immediate retry improved the UX significantly.There is another error I see pretty frequently and that is
getInfoAPI. This ticket might be about treatgetInfothe same way asblockStreambut we should consider any networking/lightwalletd errors to fall into the same bucket and generalize the solution.