Some methods may never resolve due to async race conditions and losing references about hashconnect HOT 2 CLOSED

I will look in to how to make this able to support multiple requests, for the time being you should lock the UI until the current transaction is resolved

from hashconnect.

I tried to resolve this by turning transactionResolver into a map where the key was the message's id and the value is the resolver. This should work, but the message we're sending to hashpack has a different id from the message we are receiving from hashpack. This may be intended because messages are technically different messages, but there does not seem to be a way to relate the message going to hashpack to the message coming from hashpack.

You may need to add some additional metadata to the messages that are persisted going to/from hashpack. Maybe an End-to-end ID or thread id, or something along those lines that let's hashconnect know that the messages are related and are part of the same interaction.

from hashconnect.