cryptoBeliever

Fixed in 1.0.11

It works pretty good but if it can be improved would be great. But I would avoid a lot of API calls when user typing address.

The same "issue" is on harvesting view when the user will put address but will not confirm selection from the list. Without clicking additional node on list we get "Invalid...

A similar problem is when I receive new bonded/unconfirmed transactions. Then looks like the name from the address book is taken from the confirmed transaction below unconfirmed: https://share.getcloudapp.com/kpu4rD7z

Fixed in https://github.com/symbol/desktop-wallet/pull/1847

Released (1.0.11)

We should think about priority to address book. And allow to user distinguish if name is from alias or contact.

Wallet is not showing the correct amount for mosaics (non xym) sent using alias:  https://symbol.fyi/transactions/79CDF1C23B72BA3FBD7EFB94D4DB37EF55CB8A8DD6E7209FA45F72335692C720

Current working looks like that. Transactions are first loaded with wrong "From/To" and after some time (when wallet will read all aggregate transactions) address changes to correct one. Also, this...

@bassemmagdy @yilmazbahadir maybe we can cache information fetch for aggregate (currently only correct sender). This information will not change for specific hash. Currently, each time call to API is made....