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.42-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from TestRail:#60827 Email or phone of affected tester (no customers):applausetester+rg_6@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Android 13 / Chrome, Windows 11 / Chrome App Component: Other
Action Performed:
Login using Expensifail account
Start a chat with any user
Tap the + > Split expense
Take or upload any image
Tap the Split expense
Expected Result:
Split expense should appear on chat history even though the user scan or upload any image
Actual Result:
Split expense doesn't appear on chat history when the user scan or upload any image
Note:
Split expense will appear on chat history when the user scan or uploads a valid receipt (after scanning is complete)
There New message banner will appear but truncated
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.42-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #60827
Email or phone of affected tester (no customers): applausetester+rg_6@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Android 13 / Chrome, Windows 11 / Chrome
App Component: Other
Action Performed:
Expected Result:
Split expense should appear on chat history even though the user scan or upload any image
Actual Result:
Split expense doesn't appear on chat history when the user scan or upload any image
Note:
Workaround:
Unknown
Platforms:
Screenshots/Videos
1.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @abekkala