Closed swcurran closed 1 year ago
Here's my experience with this when I tested again this evening: In terminal 1
In terminal 2
From browser localhost:4200 login click button to stage credential (the text notice in yellow came up saying ready to issue) clicked button to add to wallet (nothing happened, button click did not do anything)
console log of terminal 2 showed
Quit the browser In terminal 2
console log of terminal 2 at that point showed
Started browser localhost:4200 login
Staged the credential to add to wallet the yellow text was displayed to say ready
console log of terminal 2 showed
Clicked to add to wallet QR Code rendered
Console log of terminal 2 showed
The difference I see is that in the first attempt where it failed to generate the QR Code the console log shows its last line as a call to HTTP POST /api/patients
Where as in the second attempt that did generate a QR Code the console log does NOT have that call in the sequence of events from app start to QR Code generation.
This has been the pattern every time it fails. Whenever it fails to generate a QR Code the console log looks like the first log I listed above. The last line being HTTP POST /api/patients and then nothing more.
Overcome by events. Closing.
We've been demoing the issuer service and it's generally working well, but sometimes the QR code does not come up when clicking the issue to the wallet button. It's generally when retrying the walkthrough a second time, sometimes after stopping (
rm
andstop
) and thenstart
-ing the service. Pretty sure that a refresh of the browser solves the issue, so perhaps it is data in the browser that is out of sync with persisted data(?).We're working on getting consistent recreation instructions, but perhaps a quick scan of the code and ways that the QR code would NOT display when the button is clicked?
Thanks