In the RequestAccountInfoFlow, there is a party where the current node is asking the counter-party whether a specific account exist on the counter-party's node by:
val hasAccount = host.sendAndReceive<Boolean>(id).unwrap { it }
Here it is waiting for a Boolean value as response.
However, in the RequestAccountInfoHandlerFlow, if the specified account does exist (i.e. response != null), the counter-party does not response with a Boolean value. Instead, it will response with the transaction the contains the specified account info.
This will cause an error when requesting an account that exist on the counter-party.
In the RequestAccountInfoFlow, there is a party where the current node is asking the counter-party whether a specific account exist on the counter-party's node by:
val hasAccount = host.sendAndReceive<Boolean>(id).unwrap { it }
Here it is waiting for a Boolean value as response.However, in the RequestAccountInfoHandlerFlow, if the specified account does exist (i.e.
response != null
), the counter-party does not response with a Boolean value. Instead, it will response with the transaction the contains the specified account info.This will cause an error when requesting an account that exist on the counter-party.