Skip to content

[Due for payment 2025-07-23] [$250] Android - Scan - Multi scan "send" button doesn't register the first tap #64980

Closed

Description

@lanitochka17

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.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:

  1. Open the app
  2. Log in with an Expensifail account
  3. Open a 1:1 DM
  4. Navigate to + - Create expense - Scan
  5. Tap on the "Multi scan" button
  6. Take images of 4 receipts
  7. 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 evidence
Bug6869923_1750883466097.b.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021939611079695734924
  • Upwork Job ID: 1939611079695734924
  • Last Price Increase: 2025-07-07
  • Automatic offers:
    • nkdengineer | Contributor | 107955149
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @dylanexpensify

Activity

  1. melvin-bot commented on Jun 26, 2025

    @melvin-bot

    Triggered auto assignment to @mountiny (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  2. melvin-bot commented on Jun 26, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  3. github-actions commented on Jun 26, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jun 26, 2025
  5. mountiny commented on Jun 26, 2025

    @mountiny
    Contributor

    This is behind beta

  6. lakchote commented on Jun 27, 2025

    @lakchote
    Contributor
  7. 49 remaining items

  8. melvin-bot commented on Jul 16, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  9. melvin-bot commented on Jul 16, 2025

    @melvin-bot

    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:

  10. dylanexpensify commented on Jul 23, 2025

    @dylanexpensify
    Contributor

    Payment summary:

    Contributor: @nkdengineer $250 via Upwork
    Contributor+: @dukenv0307 $250 via NewDot

    Please apply/request!

  11. dylanexpensify commented on Jul 28, 2025

    @dylanexpensify
    Contributor

    @dukenv0307 please complete checklist

  12. dukenv0307 commented on Jul 28, 2025

    @dukenv0307
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [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

    Regression Test Proposal Template
    • [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:

    1. Open the app
    2. Log in with an Expensifail account
    3. Open a 1:1 DM
    4. Navigate to + - Create expense - Scan
    5. Tap on the "Multi scan" button
    6. Take images of 4 receipts
    7. Tap on the "Send" button
    8. Verify that: The expense should be created

    Do we agree 👍 or 👎

  13. dukenv0307 commented on Jul 28, 2025

    @dukenv0307
    Contributor

    @dylanexpensify I completed

  14. melvin-bot commented on Jul 31, 2025

    @melvin-bot

    @dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  15. flaviadefaria commented on Aug 6, 2025

    @flaviadefaria
    Contributor

    $250 Approved for @dukenv0307

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions