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
{{ message }}
This repository has been archived by the owner on May 12, 2021. It is now read-only.
Describe the bug
I'm trying to scan a disclosureRequest from a did:web identity.
The universal resolver is working fine (I get information of the public key associated), but nothing happens when I scan the QR.
If I go to the system messages, I get this:
The same code is working with did:ethr identities, so I think this is a bug.
The text was updated successfully, but these errors were encountered:
It is definitely a bug, the uPort-mobile app doesn't know about this DID method yet.
A fix for this is being worked on already, part of a larger maintenance effort.
Temporary workaround: did:web is the refactored version of did:https; they use the same mechanism but a different name.
To test your setup, until support is added here, you can use this older method name in both the DID and the corresponding DID document.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
I'm trying to scan a disclosureRequest from a did:web identity.
The universal resolver is working fine (I get information of the public key associated), but nothing happens when I scan the QR.
If I go to the system messages, I get this:
The same code is working with did:ethr identities, so I think this is a bug.
The text was updated successfully, but these errors were encountered: