Skip to content

[Due for payment 2025-11-26] Reports - Empty "From" field in preview of expense created offline on "Expenses" #75012

Closed

Description

@mitarachim

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.2.55-3
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1952/folder/13176922/41237518/1010742822
Email or phone of affected tester (no customers): ibellicotest+2049@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app)
App Component: Search

Action Performed:

Prerequisite: Account has at least one workspace.
Prerequisite 2: No expenses created yet.

  1. Open the Expensify app.
  2. Navigate to "Reports" > "Expenses"
  3. Turn off internet connection.
  4. Tap on "Create" button.
  5. Create a manual expense and submit it to any workspace.
  6. Once redirected to "Expenses" again, note that "From" field is empty. No avatar or username are displayed.

Expected Result:

When creating an expense while offline on "Expenses" section on "Reports", expense preview should automatically display the avatar of user that created expense and also the name of the user.

Actual Result:

After creating an expense while offline on "Expenses" section on "Reports", "From" field on expense preview is displayed empty. User avatar and name are not visible.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Image
Bug7002257_1762990338924.From.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @dylanexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Nov 13, 2025
  2. melvin-bot commented on Nov 13, 2025

    @melvin-bot

    Triggered auto assignment to @Christinadobrzyn (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 Nov 13, 2025

    @melvin-bot

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

  4. melvin-bot commented on Nov 13, 2025

    @melvin-bot

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

  5. github-actions commented on Nov 13, 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. self-assigned this
    on Nov 13, 2025
  7. 10 remaining items

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Nov 19, 2025
  9. changed the title [-]Reports - Empty "From" field in preview of expense created offline on "Expenses"[/-] [+][Due for payment 2025-11-26] Reports - Empty "From" field in preview of expense created offline on "Expenses"[/+] on Nov 19, 2025
  10. melvin-bot commented on Nov 19, 2025

    @melvin-bot

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

  11. melvin-bot commented on Nov 19, 2025

    @melvin-bot

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

    For reference, here are some details about the assignees on this issue:

    • @s77rt does not require payment (Contractor)
    • @dukenv0307 requires payment through NewDot Manual Requests
  12. melvin-bot commented on Nov 19, 2025

    @melvin-bot

    @dukenv0307 @dylanexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]

  13. melvin-bot commented on Nov 29, 2025

    @melvin-bot

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

  14. s77rt commented on Nov 29, 2025

    @s77rt
    Member

    No payment is required. Closing

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions