Skip to content
This repository was archived by the owner on Oct 9, 2023. It is now read-only.

Agent unable to handle issue-credential/ack-message #212

Open
lauravuo-techlab opened this issue Jan 26, 2022 · 2 comments
Open

Agent unable to handle issue-credential/ack-message #212

lauravuo-techlab opened this issue Jan 26, 2022 · 2 comments

Comments

@lauravuo-techlab
Copy link

lauravuo-techlab commented Jan 26, 2022

Agent unable to handle issue-credential/ack-message

Following error is encountered if credential ack is sent to agent:

Hyperledger.Aries.AriesFrameworkException: Couldn't locate a message handler for type did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/issue-credential/1.0/ack

To other agent is sent error 500.

Steps to reproduce the behavior:
Run interoperability tests with AATH so that dotnet-agent is playing the issuer role, e.g.

./manage build -a findy -a dotnet
./manage run -d dotnet -b findy  -t @T001-RFC0036

Expected behavior
Dotnet-agent returns 200 when credential ack is received.

@DibbsZA
Copy link

DibbsZA commented May 18, 2022

Is that just a typo on your error post because it ends in /ask and not /ack

@lauravuo-techlab
Copy link
Author

Apparently there is a typo, I reran the test and the message type findy agent sends is "ack":

Hyperledger.Aries.AriesFrameworkException: Couldn't locate a message handler for type did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/issue-credential/1.0/ack

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants