Report of broken image upload #14

Closed
opened 2024-01-25 10:13:57 -05:00 by efrick · 4 comments
Collaborator

A user at Sauve's office has reported that they tested the new version of the app, 2.3.
The user created a test referral using themselves as the patient and attaching a pan. The app uploaded the correct information for the referral but failed to upload the pan. They report no error messages during the process.

A user at Sauve's office has reported that they tested the new version of the app, 2.3. The user created a test referral using themselves as the patient and attaching a pan. The app uploaded the correct information for the referral but failed to upload the pan. They report no error messages during the process.
efrick added the
bug
label 2024-01-25 10:13:57 -05:00
Author
Collaborator

They have tested it again.
If they attempt to attach an image file it will fail.
If they attach a PDF this will attach. They did not attempt to send the referral.

They have tested it again. If they attempt to attach an image file it will fail. If they attach a PDF this will attach. They did not attempt to send the referral.
Author
Collaborator

Another potentially confusing element is that the attached PDF shows a path to the PDF.jpg thumbnail being used rather than the path of the attached file.
image

Another potentially confusing element is that the attached PDF shows a path to the PDF.jpg thumbnail being used rather than the path of the attached file. ![image](https://efrick.ddns.net/git/attachments/ec2acb32-a0de-4eb1-bb81-08eb4dac11f8)
3.2 KiB
MattBurke added this to the PatientWeb Desktop App project 2024-01-25 18:59:44 -05:00
Author
Collaborator

I verified that the image being uploaded is a jpg.
Attached is a screenshot of the file info. It was exported from VixWin which should be a common work flow.

I verified that the image being uploaded is a jpg. Attached is a screenshot of the file info. It was exported from VixWin which should be a common work flow.
Owner

The issue came from how attachment tokens were handled API side, causing the API to return a large JSON string rather than a attachment token, thus borking attachment requests. Issue has been resolved and should no longer occur.

The issue came from how attachment tokens were handled API side, causing the API to return a large JSON string rather than a attachment token, thus borking attachment requests. Issue has been resolved and should no longer occur.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MattBurke/PWAPP#14
No description provided.