department-of-veterans-affairs / va-mobile-app

"If VA were a company, it would have a flagship mobile app."
https://department-of-veterans-affairs.github.io/va-mobile-app/
16 stars 2 forks source link

BUG - All - Reports of loading attachments timing out #9304

Closed TKDickson closed 1 month ago

TKDickson commented 2 months ago

TLDR

Root cause identified. A fix was verified in staging and deployed to prod on 13-Aug-2024.

Summary of the bug

General overview of what happened and where it happened. In our July reviews, we have two reviews that reference attachments:

2024-07-28 2.32.0 iOS Constantly times out and crashes. Attachments in messages will not load and times out. 2024-07-05 2.31.0 Android Something's wrong with the app. Attachments aren't loading in the messages portal and I really need my attachment form to populate but it's not

Steps to Reproduce the Bug

Step by step instructions on how to reproduce. Be as specific as possible.

  1. Login to +226
  2. Navigate to messages and open up the message with an attachment from Feb 13, 2024. Notice that the attachment doesn't load
  3. Navigate to sent messages and open up the message with an attachment from July 31, 2024. Notice that the attachment doesn't load

Resulting behavior

What is the current behavior / experience? Attachments will not load

Expected behavior

What did you expect to happen? Attachments should load

System Information:

Screen shot, recording or additional information

Add any screen shots, video, gifs, json etc that will help the engineers track down the issue. Do not include any personally identifiable information for any real person, including screenshots.

bhanu-goparaju commented 1 month ago

Several MHV coordinators are reporting issue that Veterans are unable to open and view attachments. We are able to recreate this issue with production test accounts. ( on an iphone) Veteran has an attachment received from a Clinician in their inbox. Veteran can open the message but the attachment is not loading.. There is a icon spinning. Vetaran account has a message from July 2nd that is in their sent folder with an attachment. Same issue in the sent folder. Can open the message and read the body but the attachment is not loading. Able to open the attachment when user logs in thru VA.gov SM or MHV Classic.

DonMcCaugheyUSDS commented 1 month ago

FYI: Related Slack thread in #va-mobile-app.

bhanu-goparaju commented 1 month ago

attachment issue

DonMcCaugheyUSDS commented 1 month ago

Capture "The attachments can be opened on Va.gov and MHV Classic, but not Health and Benefits from what we are hearing."

TKDickson commented 1 month ago

Can reproduce in staging with user +226. Here's the UI experience (message with attachment icon in list, then perpetual loading spinner).

Here are the relevant backend returns, which don't include the attachments info in the 'included' section (but should, according to the OpenAPI doc):

HTTP/1.1 200 OK
Date: Mon, 12 Aug 2024 18:27:11 GMT
Content-Type: application/json; charset=utf-8
Etag: W/"6a92fdf232e0b7fba458bcd2cc16539b"
Referrer-Policy: strict-origin-when-cross-origin
Vary: Accept, Origin
X-Content-Type-Options: nosniff
X-Custom-Response-Header: eks-staging
X-Frame-Options: SAMEORIGIN
X-Git-Sha: 428d92b6783f99149ec00680a0246b3663c87f71
X-Github-Repository: https://github.com/department-of-veterans-affairs/vets-api
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: ae3d25c0-916d-4df5-bf54-08ae2982f9f1
X-Runtime: 0.408802
X-Xss-Protection: 0
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Frame-Options: SAMEORIGIN
Cache-Control: no-cache, no-store
Pragma: no-cache
Content-Encoding: gzip
Transfer-Encoding: chunked
Connection: keep-alive

{
    "data": {
        "id": "3693438",
        "type": "messages",
        "attributes": {
            "category": "OTHER",
            "subject": "General Inquiry",
            "body": "Attachment test",
            "attachment": true,
            "sentDate": "2024-06-17T11:54:03.000Z",
            "senderId": 2937955,
            "senderName": "BONTRAGER, RACHAEL J",
            "recipientId": 873433,
            "recipientName": "WEAVER, JOHNNIE LEONARD",
            "readReceipt": "READ",
            "triageGroupName": "VA Flagship mobile applications interface 1_DAYT29",
            "proxySenderName": null,
            "messageId": 3693438
        },
        "relationships": {
            "attachments": {
                "data": [{
                    "id": "3693436",
                    "type": "attachments"
                }]
            }
        },
        "links": {
            "self": "https://staging-api.va.gov/mobile/v0/messaging/health/messages/3693438"
        }
    },
    "meta": {
        "userInTriageTeam?": true
    }
}
rbontrager commented 1 month ago

Can confirm after the BE change that this is no longer reproducible on user +226 in staging and looking at related slack thread Bhanu has confirmed its no longer happening in prod as well. Closing this ticket as fixed by BE.