It might be that subscan changed their API. Having an address which had exactly a multiple of 100 of staking rewards broke the code recently. Previously, as far as I remember, that should have been fixed with @maciejhirsz PR. But maybe subscan changed something to their API and parsing an address caused this error:
I fixed the issue by not checking for the length of the list, but rather checking if it is null.
It might be that subscan changed their API. Having an address which had exactly a multiple of 100 of staking rewards broke the code recently. Previously, as far as I remember, that should have been fixed with @maciejhirsz PR. But maybe subscan changed something to their API and parsing an address caused this error:
I fixed the issue by not checking for the length of the list, but rather checking if it is null.