Open conanoc opened 3 weeks ago
Interesting use case. I think not including a service feels wrong as the service is also used to encrypt the message. But maybe it should use a service of didcomm:transport/queue (although it being queued is probably also not what you want).
I think we would have to check on the incoming message upfront if:
The scenario is as follows:
handshake: false
transport-return-route
This scenario works with an ACA-Py issuer but fails with a Credo-ts issuer.
Reasons for the failure:
getConnectionlessOutboundMessageContext()
because it cannot find a service inside the message.MessageSender.sendMessage()
becauseconnection
is null.