Closed Iskander508 closed 2 years ago
Hi @Iskander508, thanks for opening this issue.
This issue has also been reported to me by someone else already. It seems the problem has to do with the holderDid (prover_did
in the proof request). Some context:
This has been introduced by the merging of OOB/DIDExchange. We're currently using a did:peer:1 did as the holderDid (prover_did in indy-sdk) while we should be passing the public key/indy did. Weird that it would pass our own tests as indy-sdk validates the did when creating a request: https://github.com/hyperledger/indy-sdk/blob/57dcdae74164d1c7aa06f2cccecaae121cefac25/libindy/src/services/crypto/mod.rs#L406-L420
@TimoGlastra You can assign to me as I am looking into that
Using these (alpha) versions of libraries inside a react-native project:
We have tried to issue and accept a v1 credential (using an old Connection protocol 1.0). The credential offer is delivered correctly, but after accepting the offer by calling the
agent.credentials.acceptOffer
thehttps://didcomm.org/issue-credential/1.0/request-credential
message seems to be sent, although there is no answer to it (I'm not sure if it is not delivered to aca-py agent on the other side, or what is the issue).The connection was created using the
agent.oob.receiveInvitationFromUrl
method.The same issue is reproducible on both Android/iOS. In order to reproduce one can use the lissi demo. We've had no issue using the version
0.2.0-alpha.57
.debug logs (after calling the
acceptOffer
method):