(if sending crossshard transactions many times) There was a problem with receiving the transaction. At some points, the transaction data could not be read from the chain. Therefore, additional logic was written to retrieve transaction information from local storage.
But in this case, when we got the transaction data from the local storage, we didn't return anything from the function to the component, because of the wrong condition in the if.
The flow was changed: if the transaction still could not be found and get its data from the chain, I go to the local db and get the cached transaction and return it to the component.
(when you go to send after unlock) the data was transferred through the navigation state, so undefined came into the component and we could not work with it. So the logic of getting data from the state and not from the navigation was added (according to examples of how it is done in other components)
(if sending crossshard transactions many times) There was a problem with receiving the transaction. At some points, the transaction data could not be read from the chain. Therefore, additional logic was written to retrieve transaction information from local storage. But in this case, when we got the transaction data from the local storage, we didn't return anything from the function to the component, because of the wrong condition in the if. The flow was changed: if the transaction still could not be found and get its data from the chain, I go to the local db and get the cached transaction and return it to the component.
(when you go to send after unlock) the data was transferred through the navigation state, so undefined came into the component and we could not work with it. So the logic of getting data from the state and not from the navigation was added (according to examples of how it is done in other components)