-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sending a proof in an OOB invitation works on Camera/QR Code, but not ?_url deep-link #2053
Comments
@loneil trying to reproduce this, I'm assuming I need to set some config arguments or something? I'm not running into it with the default configuration |
@wadeking98 yeah I would reproduce this with VCAuth-N, think that would be easiest/applicable to the current use case. If you use VCAuth-N locally you can go into Or I can set the dev environment up to have those settings as well if you ping me. Then you could just go to a2a-dev on a mobile (but we probably wouldn't want to leave that env permanently set up like that at this time) |
I've created a PR to fix this: openwallet-foundation/bifold-wallet#1197. We're still running into an issue due to the acapy / credo empty handshake thing here: bcgov/vc-authn-oidc#583 but once that's fixed then we should be good to go |
Jason's changes actually fix this now, but to properly test you'll have to spin up vc-authn locally and comment out the |
👍 |
fixed in the latest build |
Description of problem
Using a
https://didcomm.org/out-of-band/1.1/invitation
with the proof attached is how we are doing OOB proofs in VCAuth-N.This is working successfully when scanning a QR code with the BC Wallet camera. But using the same link that the QR code resolves to, but packed into the
?_url
deep-link handler results in an "Unable to handle deep link" error:I've only tried this on Android.
Expected behavior
The link that fetches the OOB envelope works in a deep link the same as it works in the QR code, and opens the proof in the BC Wallet.
Steps to reproduce
Can use VCAuth-N with the ?_url handler enabled and the OOB invitation mode on to reproduce this. Or some other setup that will provide a redirect link to an OOB envelope with a proof request in it.
bcwallet://aries_proof-request?_url=<base64 encoded redirect url to OOB proof>
Screenshots and/or log output
OOB Deep Link with VCAuth-N
OOB.deep.link.mp4
Now, showing the same type of setup as above, but working successfully with a QR code scan
oob.camera.mp4
Environment
Build #: 1.0.18 Build(1782)
Android Device Model: Pixel 8
iOS Device Model:
Workaround
Severity
The text was updated successfully, but these errors were encountered: