Open 314159265359879 opened 2 months ago
cc @alter-eggo for ideas
hm, from the code perspective this shouldn't happen, after some time loader should resolve to Unable to load
in case of errors we try to fetch data one more time and then show this error text
on connecting issues, there should be timeout err, if I'm not mistaken after 30sec
@alter-eggo the user shared this console log. They confirmed using the latest version of the extension 6.46.0 of the wallet.
hm, seems it's browser mechanism that throttles requests by itself https://www.chromium.org/throttling/ will look more into it later
I am still trying to find out what is causing this for the user, 1 report so far. I thought the user may be experiencing a connecting issue, I don't think the shimmer effect should keep going in that case. Rather show something like "unable to load"...
When I test the dapp with the network turned off I see this: I also tried with just blocking mempool.space or bestinslot.xyz but I am unable to reproduce this issue. It will consistently show "Unable to load".
The user indicated that the balance that was shown in the wallet looked correct, even without the update that looks like it is loading.