Successful resolution. Resolving this same DID in tbdex-js works.
from @decentralgabe:
the code does not handle the case where there’s no verification method id in the DNS packet
this is a valid response, as the id can be omitted for the identity key (verification method encoded in the DID identifier itself)
Supporting Material
failing here with NPE. in the screenshot, data["id"] is null in DidDht:handleVerificationMethods()
Additional context
Hackathon users are running into this. If possible, can we get a hotfix on SDK version 2.0 that doesn't include the upgrade to protocol 2.0?
The SDK is unable to resolve a valid DID that does not contain a verification method ID in the DNS packet.
To Reproduce:
returns:
resolution: {"didDocumentMetadata":{},"didResolutionMetadata":{"error":"internalError"}}
Expected behavior:
Successful resolution. Resolving this same DID in tbdex-js works.
from @decentralgabe:
Supporting Material
failing here with NPE. in the screenshot,
data["id"]
is null inDidDht:handleVerificationMethods()
Additional context Hackathon users are running into this. If possible, can we get a hotfix on SDK version 2.0 that doesn't include the upgrade to protocol 2.0?