Skip to content

[Due for payment 2026-11-02] Android-Expense-Report name shows "Chat Report" briefly on expense opened offline via growl #102945

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.5.1-9
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: #100015
Email or phone of affected tester (no customers): ibellicotest+3215@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has a workspace.

  1. Open the Expensify app.
  2. Navigate to "Inbox"
  3. Create a manual expense via FAB and submit it to workspace chat.
  4. Return to "Inbox"
  5. Turn off internet connection.
  6. Create a second expense via FAB and submit it to workspace chat.
  7. Tap on "View" on the growl displayed.
  8. Note that when navigated to expense, report´s name is displayed as "Chat Report" for some time, before showing the correct name.

Expected Result:

Expense opened via growl should automatically show the correct title on header.

Actual Result:

Expense opened via growl while in offline mode, shows "Chat Report" briefly as title before changing to correct one.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

To be added by Applause Leads

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7276839

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 4, 2026
  2. applause-bot commented on Oct 4, 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/6474a7069c0f3716fef2965899b9c487b200b7fb94c0f755239327ee7fc2a70f

  3. melvin-bot commented on Oct 4, 2026

    @melvin-bot

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

  4. melvin-bot commented on Oct 4, 2026

    @melvin-bot

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

  5. github-actions commented on Oct 4, 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 Oct 4, 2026

    @melvin-bot

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

  7. melvin-bot commented on Oct 4, 2026

    @melvin-bot

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

  8. 21 remaining items

  9. melvin-bot commented on Oct 26, 2026

    @melvin-bot

    @situchan

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.20-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-11-02. 🎊

    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]

  10. melvin-bot commented on Oct 29, 2026

    @melvin-bot

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

  11. melvin-bot commented on Nov 1, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  12. melvin-bot commented on Nov 1, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  13. mountiny commented on Nov 2, 2026

    @mountiny
    Contributor

    This was a follow up

  14. situchan commented on Nov 9, 2026

    @situchan
    Contributor

    This was actually not a regression from #100015.
    The bug was reproducible on production playstore app v9.4.99.2 before #100015, while this was reported in v9.5.1-9.
    So I think I am eligible for payment.

  15. mallenexpensify commented on Nov 9, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @situchan due $175 via NewDot

    @mountiny, comment/reopen if you disagree. From Claude

    Claude posting on behalf of Matt:

    @situchan is due $175, ie. 100% of the $175 job price. #100015 did not cause this bug. Julesssss demoted the blocker after situchan showed the bug on production v9.4.99-2. @mountiny, can you confirm? Your "This was a follow up" reads as $0.

    Evidence

    Claude posting on behalf of Matt. PAYRUBRICTEST v1

  16. laurenreidexpensify commented on Nov 11, 2026

    @laurenreidexpensify
    Contributor

    Approved $175 @situchan New Expensify

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 productionBugSomething 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