Skip to content
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

After issuing VC via CHAPI, LCW shows error #547

Closed
alexfigtree opened this issue Jan 24, 2024 · 7 comments
Closed

After issuing VC via CHAPI, LCW shows error #547

alexfigtree opened this issue Jan 24, 2024 · 7 comments
Assignees
Labels
bug Schedule this bug Build82

Comments

@alexfigtree
Copy link
Contributor

alexfigtree commented Jan 24, 2024

Steps to reproduce:

  1. Go through wallet setup again. (Uninstall / reinstall app, or go to Settings > Reset Wallet, and relaunch the app).
  2. This time, don't skip the Register step. Click on Register Wallet. You'll be taken to the register web page. click Register there. Then switch back to the wallet
  3. Now lets get a VC into the wallet (from flow 1).
  4. Go to https://vcplayground.org/issuer (in your mobile browser)
  5. In the upper right of the playground issuer webpage, click the Settings gear, select VC-API to any Wallet
  6. Click Issue Verifiable Credential blue button.
  7. Click Skip DID Authentication

This should open LCW and present you with the VC, and an Accept/Decline screen. Error is seen here.

Seeing this in iOS:

screenshot_2024-01-23_at_1 47 07___pm

Originally posted by @alexfigtree in #263

@alexfigtree alexfigtree changed the title After issuing VC, LCW shows error After issuing VC via CHAPI, LCW shows error Jan 24, 2024
@alexfigtree alexfigtree moved this to To Do (Current sprint) in DCC Engineering Jan 24, 2024
@dmitrizagidulin dmitrizagidulin added the bug Schedule this bug label Feb 7, 2024
@dmitrizagidulin dmitrizagidulin moved this from To Do (Current sprint) to In Progress in DCC Engineering Feb 7, 2024
@alexfigtree alexfigtree moved this from In Progress to Ready for Review in DCC Engineering Feb 21, 2024
@dmitrizagidulin
Copy link
Contributor

This has been fixed in the RN branch, PR #550

@alexfigtree
Copy link
Contributor Author

@dmitrizagidulin Just tested this. Error is still happening, showing the same screenshot as above. Tested on iOS. Moving back to ToDo.

@alexfigtree alexfigtree moved this from Ready for PR Review/re-test to To Do (Current sprint) in DCC Engineering Mar 25, 2024
@alexfigtree alexfigtree moved this from To Do (Current sprint) to Done (Deployed) in DCC Engineering Apr 24, 2024
@alexfigtree alexfigtree self-assigned this Apr 24, 2024
@alexfigtree alexfigtree moved this from Done (Deployed) to Ready for PR Review/re-test in DCC Engineering Apr 24, 2024
@alexfigtree alexfigtree moved this from Ready for PR Review/re-test to Release Ready in DCC Engineering May 2, 2024
@alexfigtree alexfigtree moved this from Release Ready to Done (Deployed) in DCC Engineering May 2, 2024
@alexfigtree
Copy link
Contributor Author

Currently waiting on merge to main

@alexfigtree
Copy link
Contributor Author

Re-testing needed on build 81

@alexfigtree alexfigtree moved this from Done (Deployed) to Ready for PR Review/re-test in DCC Engineering Sep 4, 2024
@alexfigtree
Copy link
Contributor Author

alexfigtree commented Sep 12, 2024

Build 81: Not showing error, but also not reflecting in the app. Currently see the option of choosing between many wallets (Veres demo) before getting to LCW. Could also be blocked by #638 .

@alexfigtree
Copy link
Contributor Author

Build 82: Works in iOS, although the cred being imported is missing info:

Image
Image

@alexfigtree alexfigtree moved this from Ready for PR Review/re-test to Release Ready in DCC Engineering Sep 24, 2024
@alexfigtree alexfigtree moved this from Release Ready to Done (Deployed) in DCC Engineering Oct 10, 2024
@alexfigtree
Copy link
Contributor Author

Issue complete, moving to Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Schedule this bug Build82
Projects
None yet
Development

No branches or pull requests

3 participants