I've been working with the Trustbloc Sandbox and followed the steps mentioned in this guide. This issue occurs both in my local k8s environment and the staging environment mentioned in the guide.
Steps to Reproduce
Start the wallet normally.
Proceed to the issuer flow.
Reach the last step before actually issuing the verifiable credential.
Expected Behavior
The verifiable credential should be issued without errors and appear in wallet initialized in step 1.
Actual Behavior
I get an error message: failed to create verifiable credential: 404 Not Found: 404 page not found.
Additional Information
Here is the screenshot of the error, showcasing the URL where the error occurred.
Severity and Impact
This bug has become quite the roadblock in our evaluation process of Trustbloc products (vcs and wallet-sdk) for potential adoption. Given that we're seeing this in both local and staging environments, it seems like a core issue that might be affecting other users or potential adopters as well. Solving this could not only unblock us but also smooth out the experience for everyone.
We've tried a bunch of things but can't seem to crack this. If anyone could lend a hand or point us in the right direction, that would be amazing!
I've been working with the Trustbloc Sandbox and followed the steps mentioned in this guide. This issue occurs both in my local k8s environment and the staging environment mentioned in the guide.
Steps to Reproduce
Expected Behavior
The verifiable credential should be issued without errors and appear in wallet initialized in step 1.
Actual Behavior
I get an error message:
failed to create verifiable credential: 404 Not Found: 404 page not found.Additional Information
Here is the screenshot of the error, showcasing the URL where the error occurred.
Severity and Impact
This bug has become quite the roadblock in our evaluation process of Trustbloc products (vcs and wallet-sdk) for potential adoption. Given that we're seeing this in both local and staging environments, it seems like a core issue that might be affecting other users or potential adopters as well. Solving this could not only unblock us but also smooth out the experience for everyone.
We've tried a bunch of things but can't seem to crack this. If anyone could lend a hand or point us in the right direction, that would be amazing!