-
Notifications
You must be signed in to change notification settings - Fork 132
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
The execution never continue after calling agent.handleMessage
#281
Comments
More on this issue... When trying to process this SDR: I got this error:
An important point to mention: when I attach to a debugger, the error does not show and the process goes smoothly for both reading and SDR and creating claims in addition to sending the SDR approval to the issuer endpoint. |
Thank you for the clarification. Can you see if the solution from this bug changes something for you? From the perspective of DAF it is still a bug that the error is swallowed and the |
Thanks Mircea, I added Regarding the stack trace,
And I could not find that DAF has tests for DAF React Native packages. Both https://github.com/uport-project/daf/tree/master/packages/daf-react-native-libsodium and https://github.com/uport-project/daf/tree/master/packages/daf-react-native-async-storage do not seem to have tests. However, in our case we are only using |
@Muhammad-Altabba is this still an issue in the latest veramo? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bug severity
5
Describe the bug
Not being able to get the processed message after calling
agent.handleMessage
(the execution never continue). We started to have this after migrating from Daf 5 to Daf 6. (Early data was all erased by deleting the Mobile App and clearing the cache)To Reproduce
Steps to reproduce the behavior:
Note: Trying to tace the bug origin. The method that produces the issue is
await verifyJWT
that is called insideJwtMessageHandler -> handle
. And when addingconsole.log(e)
The following was logged:Setup Configuration
Versions:
The text was updated successfully, but these errors were encountered: