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
Version Number: 9.1.8-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both Email or phone of affected tester (no customers):ibellicotest+345@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome App Component: Other
Action Performed:
Open the Expensify app.
Open any chat.
Tap on the "+" button and select "Add Attachment"
Tap on "Choose File" and select any video.
Tap on "Send"
Once redirected to chat, long tap on the video and select "Reply in thread"
Once inside the thread, open the video.
Tap on play.
Check if the video can be played.
Expected Result:
User should be able to reproduce a video when inside a thread.
Actual Result:
User is unable to reproduce a video attachment when inside a thread.
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.1.8-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
Email or phone of affected tester (no customers): ibellicotest+345@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Other
Action Performed:
Expected Result:
User should be able to reproduce a video when inside a thread.
Actual Result:
User is unable to reproduce a video attachment when inside a thread.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6760590_1741065469782.Video_Thread.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @abekkala