You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open expensify app and send an attachement from Account 1 to a group with previous attachement history with Account 2 and 3 as members
Go to the attached file using account 2 and flag the attachement "assault"
Observe that the attachement is removed from the chat history
Now go to account 3 and open the attachement preview by clicking on any other attachements sent prior to the flagged attachement
Swipe to the left and observe that the flagged attachement can be viewed and downloaded from attachement preview even if it was removed
Expected Result:
Flagged attachements shouldnt have been accessed once removed
Actual Result:
flagged attachement can be viewed and downloaded from attachement preview even if it was removed
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android / native
Android / Chrome
iOS / native
iOS / Safari
MacOS / Chrome / Safari
MacOS / Desktop
Version Number: 1.3.32-5 Reproducible in staging?: y Reproducible in production?: y If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Notes/Photos/Videos: Any additional supporting documentation
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Flagged attachements shouldnt have been accessed once removed
Actual Result:
flagged attachement can be viewed and downloaded from attachement preview even if it was removed
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.32-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.20230626.204615.Chrome.mp4
2023_06_21_05_53_26.mp4
Expensify/Expensify Issue URL:
Issue reported by: @SofoniasN
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687361182231919
View all open jobs on GitHub
Upwork Automation - Do Not Edit