Skip to content

[Due for payment 2026-08-31] Android - Expense - No growl after splitting/bulk duplicating expense #99252

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.59-0
Reproducible in staging?: Yes
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 BrowserStack: #96496
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Money Requests

Action Performed:

  1. Launch Expensify app.
  2. Go to Inbox.
  3. Create an expense from FAB.
  4. Open the expense.
  5. Tap More > Split > Save.

Expected Result:

Growl will appear after splitting an expense.

Actual Result:

Growl does not appear after splitting an expense.

This issue also happens when bulk duplicating expense.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7239801_1787372473048.Screen_Recording_20260822_121937_Expensify.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7239801

Issue OwnerCurrent Issue Owner: @situchan

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 22, 2026
  2. applause-bot commented on Aug 22, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/e6b950fbb3ad99563c9de6065cc814fa41018097d06f3928333790cf20e80cff

  3. melvin-bot commented on Aug 22, 2026

    @melvin-bot

    @mountiny recently merged #96496, but they are OOO right now, so I'll auto-assign someone else.

  4. melvin-bot commented on Aug 22, 2026

    @melvin-bot

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

  5. github-actions commented on Aug 22, 2026

    @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. melvin-bot commented on Aug 22, 2026

    @melvin-bot

    @mountiny @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #96496

  7. melvin-bot commented on Aug 22, 2026

    @melvin-bot

    @mhawryluk you have been assigned to this deploy blocker because you authored the offending PR: #96496

  8. 7 remaining items

  9. mhawryluk commented on Aug 24, 2026

    @mhawryluk
    Member

    expected, we keep the highlight here

  10. mountiny commented on Aug 24, 2026

    @mountiny
    Contributor

    @mhawryluk we should not be showing the growl in this case since we remained in Inbox, right?

    Image
  11. mhawryluk commented on Aug 24, 2026

    @mhawryluk
    Member

    my implementation did intend to show it in this scenario. we don't show the growl on Inbox when we're on a report view with a table of expenses:

    Image

    that's what I gathered from the past discussion, but I'm happy to change it in v2 if we want. though we can see that we don't always highlight the new expense in the chat view, so I think the growl is indeed expected here (though we don't remove the highlight here ourselves, so no growl would match the current behavior, not regress anything)

  12. mountiny commented on Aug 24, 2026

    @mountiny
    Contributor

    Ok but then there was no growl on web when the expense was created in inbox here #99262

    Image

    Which feels like the same flow so I think we should either show the growl in both or in neither

  13. mhawryluk commented on Aug 24, 2026

    @mhawryluk
    Member

    in the linked flow the expense was not created from FAB, but from the + next to the composer, so no growl

  14. changed the title [-]Android - Expense - No growl after splitting/bulk duplicating expense[/-] [+][Due for payment 2026-08-31] Android - Expense - No growl after splitting/bulk duplicating expense[/+] on Aug 24, 2026
  15. melvin-bot commented on Aug 24, 2026

    @melvin-bot

    @situchan

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.59-5 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 2026-08-31. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  16. melvin-bot commented on Aug 27, 2026

    @melvin-bot

    @situchan Whoops! This issue is 2 days overdue. Let's get this updated quick!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions