No Connection Associated with Incoming Message After DID Rotation

[tipusinghaw]

I am working on migrating a specific tenant from a shared multi-tenant wallet to a dedicated wallet using askar-tools-typescript. I successfully decoupled the tenant and attempted to rotate the DID to maintain communication with an existing connection.
To achieve this, I made modifications to getDidDocumentForCreatedDid,added this to resolve external DIDs.It only checks in the local did repository instead of resolving a did.
After implementing this change, DID rotation worked successfully. However, when attempting to communicate with the older connection, the message is received at the new location, but this error is occurred no connection is associate the incoming message.

Upon reviewing the logic, I believe additional modifications are required to properly handle connection resolution post-DID rotation. I would be happy to contribute a fix with proper guidance and clarification.

[genaris]

Hey @tipusinghaw , is it possible for you to share some code to make it simpler for us to understand the context and the changes you had to do?

[tipusinghaw]

Thank you for your response, @genaris. To reproduce this issue, I need to perform multiple steps, so I will create a script for that. In the meantime, I have a screenshot of the issue that might be helpful.