You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an agent accepts a proof request, the ProofsApi automatically sets up mediation for the presentation message it sends back to the verifier (requester), due to this code in the Proofs API: https://github.com/hyperledger/aries-framework-javascript/blob/main/packages/core/src/modules/proofs/ProofsApi.ts. It doesn't call getRouting with useDefaultMediator: false. This means it will fail if no internet is present, and it will also fail with the return routing response.
When receiving an OOB invitation, we want to be able to pass an optional routing prop along with the invitation. This routing prop is only used when creating a connection. If we can somehow store this routing, we could use it instead of creating new routing in the ProofsApi acceptRequest method.
When an agent accepts a proof request, the
ProofsApi
automatically sets up mediation for the presentation message it sends back to the verifier (requester), due to this code in the Proofs API: https://github.com/hyperledger/aries-framework-javascript/blob/main/packages/core/src/modules/proofs/ProofsApi.ts. It doesn't call getRouting withuseDefaultMediator: false
. This means it will fail if no internet is present, and it will also fail with the return routing response.When receiving an OOB invitation, we want to be able to pass an optional
routing
prop along with the invitation. This routing prop is only used when creating a connection. If we can somehow store this routing, we could use it instead of creating new routing in the ProofsApiacceptRequest
method.This issue is related to #1250.
The text was updated successfully, but these errors were encountered: