Skip to content

[Due for payment 2025-03-25] [$250] Reports - After disabling internet, via switcher selecting diff. WS displays you appear offline #57463

Closed

Description

@IuliiaHerets

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: V9.1.6-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue reported by: Applause Internal Team
Device used: Redminote 10s android 13
App Component: Left Hand Navigation (LHN)

Action Performed:

  1. Go to https://staging.new.expensify.com/home
  2. Tap reports
  3. Turn off internet
  4. Tap expensify switcher and select different workspace

Expected Result:

After disabling internet, via switcher selecting different WS must not display "you appears to be offline" in reports page.

Actual Result:

After disabling internet, via switcher selecting different WS displays "you appears to be offline" in reports page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6754925_1740567980470.Screenrecorder-2025-02-26-16-28-14-678.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021899316495200659491
  • Upwork Job ID: 1899316495200659491
  • Last Price Increase: 2025-03-11
  • Automatic offers:
    • daledah | Contributor | 106508740
Issue OwnerCurrent Issue Owner: @MitchExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 26, 2025
  2. melvin-bot commented on Feb 26, 2025

    @melvin-bot

    Triggered auto assignment to @MitchExpensify (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. moved this to Upcoming Cohorts in [#whatsnext] #migrateon Mar 1, 2025
  4. MitchExpensify commented on Mar 1, 2025

    @MitchExpensify
    Contributor

    I think this is migrate because it will impact companies with multiple workspaces. Companies with multiple workspaces are not the simplest use case so it is a future cohort

  5. melvin-bot commented on Mar 4, 2025

    @melvin-bot

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

  6. melvin-bot commented on Mar 6, 2025

    @melvin-bot

    @MitchExpensify Huh... This is 4 days overdue. Who can take care of this?

  7. melvin-bot commented on Mar 10, 2025

    @melvin-bot

    @MitchExpensify 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    ExternalAdded to denote the issue can be worked on by a contributor
    on Mar 11, 2025
  9. melvin-bot commented on Mar 11, 2025

    @melvin-bot
  10. changed the title [-]Reports - After disabling internet, via switcher selecting diff. WS displays you appear offline[/-] [+][$250] Reports - After disabling internet, via switcher selecting diff. WS displays you appear offline[/+] on Mar 11, 2025
  11. 32 remaining items

  12. changed the title [-][$250] Reports - After disabling internet, via switcher selecting diff. WS displays you appear offline[/-] [+][Due for payment 2025-03-25] [$250] Reports - After disabling internet, via switcher selecting diff. WS displays you appear offline[/+] on Mar 18, 2025
  13. melvin-bot commented on Mar 18, 2025

    @melvin-bot

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

  14. melvin-bot commented on Mar 18, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.14-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 2025-03-25. 🎊

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

  15. melvin-bot commented on Mar 18, 2025

    @melvin-bot

    @dukenv0307 @MitchExpensify @dukenv0307 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]

  16. dukenv0307 commented on Mar 19, 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: This is an edge case

    • [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

    Regression Test Proposal

    Test:

    1. Go offline
    2. Go to Reports
    3. Go to a search that has not viewed yet
    4. Verify that: Offline indicator on bottom is not shown

    Do we agree 👍 or 👎

  17. MitchExpensify commented on Mar 25, 2025

    @MitchExpensify
    Contributor

    Payment summary:

  18. MitchExpensify commented on Mar 25, 2025

    @MitchExpensify
    Contributor

    Payment for @dukenv0307 is all that is left here, closing

  19. moved this from Upcoming Cohorts to Done in [#whatsnext] #migrateon Mar 25, 2025
  20. JmillsExpensify commented on Mar 26, 2025

    @JmillsExpensify
    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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions