Coordinate fix for mobile app API error currently blocking sign-in for LOA1 MHV accounts (replace with correct alert)

[laurwill]

Problem currently happening: When a Veteran signs in to the VAHB mobile app with an unverified LOA1 MHV "basic" account, they encounter an API error screen with no recovery step. Here's this authentication flow and error state as documented by @sterkenburgsara . I independently confirmed this error is happening by signing in to mobile app with my MHV basic account.

What we think should happen instead: When a Veteran signs in to the VAHB mobile app with an unverified LOA1 MHV "basic" account, they should encounter this recently approved variation of the sign-in alert, currently being standardized/componentized in VADS. This alert explains that they must use an identity-verified account. Since they cannot verify identity for their MHV account, it instructs them to use a Login.gov or ID.me account instead.

Suggested content adjustment to alert: In step 1, change "Sign out of VA.gov" to "Sign out of the mobile app."

Questions:

• This authentication flow is specific to the mobile app, but it happens in web through VA.gov sign-in modal. Which team is responsible for implementing the correct alert?
• Do we need to adjust the content in the approved alert in any other way for this mobile app-specific authentication flow?

[laurwill]

Update: @joeniquette @joellewells are opening a change request ticket with the mobile app team to address this fix. Joe and Joelle, please let me know if you need anything else from me or @mistymg on this, and thank you!