-
Notifications
You must be signed in to change notification settings - Fork 61
Description
In digital business card usage we use the appropriate goal code for the connection-attest-offer flow. But the "offer" part can in some cases need to wait for user feedback
When I issue a DBC, in the case where the user must confirm their identity with a popup, the flow is the following after QR scan:
- Connection request is made and then established
- Attestation credential is checked (are you a BC Wallet?)
- BCROS holds waiting for the user to respond to popup before offer
- Offer is made to wallet
- User confirms the identity or not (both steps move to offer but attributes will vary based on popup response)
This uses the aries.vc.issue
goal code so the wallet holds on the credential offer loading UI until the offer, so that the user doesn’t see the various steps independently (which is good). But since “BCROS holds waiting for the user to respond” can be an independent amount of time, the wallet interprets the process as “being slow” so pops the info banner below:

So there's, at least here, use cases where the issuance UX can sit without being related to a slow internet connection, but the user gets a message that it's unexpectedly slow while waiting for their feedback.
Not sure if anything can be done with this, or just if the messaging could be more generic or something?