Crypto Pank

yes, it might be, but just tried and i able to see token images

yes, right, i tried with with simulating rate limitted error, and able to see same issue, looks like we override existed data with fallback, when we are now able to...

maybe it better to remove this line? `.catch { _ in return strongSelf.generateTokenJsonFallback(for: tokenId, tokenType: tokenType, address: address) }`

even if tokenUri() returns a url that works, the request with that url might fail, in this case we replace failure response with fallback data. we actually replace failure case...

A) the result is stored, we never call tokenUri()again to get the updated URI (they fixed it) and get the JSON we always call tokenUri() when trying to get json...

> So if we always call tokenUri() to get the current URL, it should work for me right? yes

Fixed some crushes, and memory leaks, checked Wallet Connect v.2 updated version with dapp `https://lab.web3modal.com`, connection works ok, only thing i found that when switching chains, in dapp it doesn't...

@hboon at this point it should be good 1e17a6b36b278e2daa39551db288a68291a67abc

> Sounds useful. So request background time if there’s an active WalletConnect session? Want to try it out? actually don't know for now, it needs to check.

> But wait. Doesn’t the universal link for AlphaWallet get triggered and the apps switched to for signing requests? it the app get triggered by universal link (and its in...