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
{{ message }}
Repository navigation
[Due for payment 2025-07-23] [$250] Android - Scan - Multi scan "send" button doesn't register the first tap #64980
Version Number: 9.1.71-0 Reproducible in staging?: Y Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from TestRail:#63848 Issue reported by: Applause - Internal Team
Action Performed:
Open the app
Log in with an Expensifail account
Open a 1:1 DM
Navigate to + - Create expense - Scan
Tap on the "Multi scan" button
Take images of 4 receipts
Tap on the "Send" button
Expected Result:
The expense should be created
Actual Result:
Multi scan "send" button doesn't register the first tap after taking pictures of a few receipts. The tap animation is visible but nothing happens after. It works on the second or third try
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6869923_1750883466097.b.mp4
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.81-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. Yes
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Jun 26, 2025
Triggered auto assignment to @mountiny (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 26, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 26, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
mountiny commentedon Jun 26, 2025
This is behind beta
lakchote commentedon Jun 27, 2025
cc @dylanexpensify @cristipaval @Swor71 @VickyStash
49 remaining items
melvin-bot commentedon Jul 16, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 16, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.81-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-07-23. 🎊
For reference, here are some details about the assignees on this issue:
dylanexpensify commentedon Jul 23, 2025
Payment summary:
Contributor: @nkdengineer $250 via Upwork
Contributor+: @dukenv0307 $250 via NewDot
Please apply/request!
dylanexpensify commentedon Jul 28, 2025
@dukenv0307 please complete checklist
dukenv0307 commentedon Jul 28, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: https://github.com/Expensify/App/pull/61574/files#r2235177633
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. Yes
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
dukenv0307 commentedon Jul 28, 2025
@dylanexpensify I completed
melvin-bot commentedon Jul 31, 2025
@dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
flaviadefaria commentedon Aug 6, 2025
$250 Approved for @dukenv0307