Closed OmarB97 closed 3 years ago
Thanks for reporting! There was a bug when receiving that did not resolve the actual amount. This is fixed in v1.2.0. Can you try upgrading to that version?
Hey sorry for the late response, tested on 1.2.0 yesterday and I think it works now :)
Thanks for testing!
This is the resolved account object that we get back in the promise after calling the recieve() api:
{account: Proxy, resolvedCount: 1} account: Proxy
address: "hidden-for-privacy-reasons" balance: undefined privateKey: "hidden-for-privacy-reasons" publicKey: "hidden-for-privacy-reasons" representative: "nano_1kaiak5dbaaqpenb7nshqgq9tehgb5wy9y9ju9ehunexzmkzmzphk8yw8r7u" proto: Object
resolvedCount: 1 proto: Object
The balance seems to come back as undefined, although the block does seem to still get processed and I get the receive subscription for the processed block from my WebSocket afterward, so seems like somewhere the balance is just not getting assigned properly (?)