-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fix behaviour when invoked through deep links. #1267
Labels
Comments
Duplicate of #1223? Or at least related, we should consolidate it into one issue? |
Definitely related. We could set a tag / milestone for deep linking improvements. Although this one certainly holds priority. |
@Exulansis is this still an issue? |
It's no longer relevant. Can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If the wallet is invoked by some external application via a deep link, it does not always return control to the calling application. This depends on the callback specified in the
callbackURL
field of the interaction token.To Reproduce
Steps to reproduce the behavior:
http
callbackURL
(e.g.https://myservice.com/authentication
)Expected behavior
The wallet should invoke the initial calling application, regardless of the
callbackURL
The text was updated successfully, but these errors were encountered: