You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
The page should show all assets an account owns.
Additional context
This is caused by a change on the get_full_accounts API introduced in BitShares Core 3.2.0 release.
See bitshares/bitshares-core#1808:
The get_full_accounts API
will return different fields: two fields (withdraws and htlcs) have been removed and are replaced by four fields (withdraws_from, withdraws_to, htlcs_from, htlcs_to);
lists returned by the API are limited to certain sizes (configurable by node operator), a more_data_available field is added to indicate what lists are incomplete due to the limit. Clients need to call other APIs to query for next pages of data.
The text was updated successfully, but these errors were encountered:
The same issue applies to open orders. If a user has more than 100 open orders, the UI doesn't show all of them, also the data in "in orders" column of portfolio page would be incorrect.
abitmore
changed the title
Portfolio does not show all assets
Portfolio does not show all assets, nor count in all open orders
Mar 1, 2020
bitshares-js provides a new method for this, currently only supporting "balance". This needs to be extended to open orders to fix #3248 and both implemented in the UI
Describe the bug
See https://wallet.bitshares.org/#/account/president-jiang , as of writing, the page shows "Total of 93 assets". According to
https://cryptofresh.com/u/president-jianghttps://blocksights.info/#/accounts/1.2.539130, the account holds balances of more than 100 assets(although data on CF could be stale).Expected behavior
The page should show all assets an account owns.
Additional context
This is caused by a change on the
get_full_accounts
API introduced in BitShares Core 3.2.0 release.See bitshares/bitshares-core#1808:
The text was updated successfully, but these errors were encountered: