...
iOS | MacOS | Android | Linux | Windows | |
|---|---|---|---|---|---|
FIO Token | |||||
Create FIO wallet | luke: okay | Eric: okay PM: OK | |||
Check FIO balance | luke: okay | Eric: okay PM: OK | |||
Transfer FIO | luke: okay | Eric: okay PM: OK | |||
FIO Transaction history | luke: okay | Eric: okay PM: OK | |||
Import FIO Private Key | |||||
Import mnemonic phrase | |||||
FIO Addresses | |||||
Register FIO Address on wallet domain (api or link to reg site) | luke: okay | Eric: okay PM: OK | |||
Renew FIO address | |||||
Display registered FIO Addresses | luke: okay | Eric: okay PM: OK | |||
Register FIO Address on custom domain | |||||
FIO Domains | |||||
Register custom FIO Domain (api or link to reg site) | |||||
Renew FIO Domain | |||||
Display registered FIO Domains | |||||
Transfer FIO Domain | |||||
FIO Send | |||||
Send crypto using FIO Address | luke: okay | PM: OK | |||
Send to multi-level blockchain public address | |||||
FIO Receive | |||||
Receive crypto using FIO Address (via direct send) | luke: okay | Eric: okay PM: OK | |||
Map FIO Address to NBPA | luke: can’t map Monero, others work | Some issues with mapping, see below. PM: OK | |||
FIO Request | |||||
Submitting new FIO Request | luke: okay | Eric: okay PM: OK | |||
Rejecting a FIO Request | luke: okay | Eric: okay PM: OK | |||
List pending FIO Requests | luke: okay | Eric: okay PM: OK | |||
List sent FIO Requests | luke: okay | Eric: okay PM: OK | |||
Cancel FIO Requests | |||||
FIO Data | |||||
Memo field for FIO Requests | luke: okay | Eric: okay PM: OK | |||
Record OBT on direct Send of FIO when both users have FIO Addresses | luke: shows up in the interface, but isn’t sent | ||||
Retrieving and displaying OBT data |
Issues
15-Oct-2020 Eric
On the FIO Requests screen, it would be helpful to show the status of the Sent Requests. Other wallets shown "received" "pending" or "rejected". This information shows up in Request Details, but that is an extra step.
When you are in FIO the back arrow always takes you back to the main wallets home page. Is that by design? For example, If I look at my FIO requests, and then look at the detail of a fio request, shouldn't the back arrow take me back to the FIO requests list?
On Manage Address, you should not allow the FIO Address to be unmapped. It is used for other fio transactions.
I am getting an "Error happened on pushing transaction to chain" error when attempting to unmap an address. This worked before so is a regression.
On Manage Address, when I have multiple wallets of the same coin (like ETH) there is a dropdown to select the wallet I want to map. FIO only allows mapping a FIO Address to one wallet of each coin type. So, we need to be sure that if an ETH wallet is already mapped, it does not allow the user to map another one. Also, if I have an ETH#1 wallet mapped and then select ETH#2 from the drop down, the slider indicator does not change (it shows it as mapped). When selecting wallets from the dropdown, the slider should change status indicating whether it is or is not mapped (and, again, it should not allow a user to map a second ETH wallet, etc.)