Skip to content

[HOLD on #59245] [$250] Hybrid iOS - Track - Tapping the back button after moving an expense, opens the self DM twice #58224

Closed

Description

@vincdargento

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.11-3
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: iPhone 13/ 18.3.1
App Component: Chat Report View

Action Performed:

Precondition: The self DM should not have any messages.

  1. Open the app
  2. Navigate to the Self DM
  3. Click on the + on compose box
  4. Choose Track expense
  5. Create a manual expense for $1
  6. Create the expense
  7. On the actionable whisper options, select Submit to someone
  8. Select the participant and end the flow
  9. Tap the back arrow in the left upper corner

Expected Result:

The self DM doesn't appear for the second time when tapping the back button

Actual Result:

Tapping the back button after moving an expense using actionable menu, opens the self DM twice. Sometimes, when the Self DM is opened for the second time, it has a blank background

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021899513850408399173
  • Upwork Job ID: 1899513850408399173
  • Last Price Increase: 2025-03-25
Issue OwnerCurrent Issue Owner: @twisterdotcom

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 11, 2025
  2. melvin-bot commented on Mar 11, 2025

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. melvin-bot commented on Mar 11, 2025

    @melvin-bot

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

  4. melvin-bot commented on Mar 11, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 11, 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.
  6. vincdargento commented on Mar 11, 2025

    @vincdargento
    Author

    @mallenexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. 49 remaining items

  8. added and removed
    Help WantedApply this label when an issue is open to proposals by contributors
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Apr 1, 2025
  9. mallenexpensify commented on Apr 14, 2025

    @mallenexpensify
    Contributor

    @twisterdotcom thanks for keeping 👀 on, I unassigned ya.

    Also... going to try to find other 'back button' issues and link to the #59245

  10. adamgrzybowski commented on May 5, 2025

    @adamgrzybowski
    Contributor

    @mallenexpensify I couldn't sleep since you found the glitching on the report screen 😄
    So I created an issue for that #61379

    So far, I've only been able to reproduce this on a simulator. I've found other ways to reproduce this problem, but none of them are 100% effective. Do you remember if the video you sent here was from a simulator or a physical device?

  11. mallenexpensify commented on May 6, 2025

    @mallenexpensify
    Contributor

    Tried to reproduce the steps you outlines, with no luck. Commented on the issue.

  12. melvin-bot commented on Jul 18, 2025

    @melvin-bot

    @puneetlath, @Ollyws, @mallenexpensify, this Monthly task hasn't been acted upon in 6 weeks; closing.

    If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

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

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions