Skip to content

Status - Status reverts to previous status or turns blank when going offline after saving #24423

Closed

Description

@lanitochka17

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

Precondition: Set different status and erase it before running the steps

  1. Launch New Expensify app
  2. Go to Settings > Profile > Status
  3. Add a status and save it
  4. Immediately go offline

Expected Result:

When going offline, the status remains as is

Actual Result:

When going offline, the status either reverts to a previous status (precondition) or it becomes blank

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.53.1

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6161049_Screen_Recording_20230811_104449_New_Expensify.1.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. OSBotify commented on Aug 11, 2023

    @OSBotify
    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.
  2. melvin-bot commented on Aug 11, 2023

    @melvin-bot

    Triggered auto assignment to @amyevans (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  3. conorpendergrast commented on Aug 11, 2023

    @conorpendergrast
    Contributor

    @lanitochka17 I don't think that's the correct video, could you check?

  4. 0xmiroslav commented on Aug 11, 2023

    @0xmiroslav
    Contributor

    Custom status bugs are not blockers.
    Context: https://expensify.slack.com/archives/C049HHMV9SM/p1691610130667239

  5. amyevans commented on Aug 11, 2023

    @amyevans
    Contributor

    Yeah the attached video isn't correct but I reproed with the test steps. But as @0xmiroslav pointed out (thanks!) this is a feature under active development so we won't consider them blockers. Assigning over to @stitesExpensify to handle in the context of that project!

  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Aug 11, 2023
  7. stitesExpensify commented on Aug 11, 2023

    @stitesExpensify
    Contributor
  8. 22 remaining items

  9. stitesExpensify commented on Oct 16, 2023

    @stitesExpensify
    Contributor

    Any updates here?

  10. perunt commented on Oct 23, 2023

    @perunt
    Contributor

    @lanitochka17, do you use any throttle tools?
    I've tried it with the slow 3g, and even then, it was way faster than your network.
    I assume it is related to the request queue. When it fails when you go offline, it can remove optimistic data. But I'm still in the testing process.

    clideo_editor_ba738351f42b430895074a5f4b9aaffd.mp4
  11. stitesExpensify commented on Nov 3, 2023

    @stitesExpensify
    Contributor
  12. lanitochka17 commented on Nov 4, 2023

    @lanitochka17
    Author

    @perunt Hello. most likely the issue was reproduced with low Internet traffic
    Issue is not reproducible on build 1.3.95-5

    0-02-01-b0c5d6408a318113fa4ff47b5b0aacf14cf38a70b58c2659a6106a9a03fdc625_e2e0e34b64fb00dc.mp4
  13. perunt commented on Nov 6, 2023

    @perunt
    Contributor

    From what I saw, there is a problem with the queue. Also, I remember recently that the queue was changed a bit. So, it's probably related.
    Do I get you right? Is it no more reproducible in newer builds?

  14. stitesExpensify commented on Nov 14, 2023

    @stitesExpensify
    Contributor
  15. stitesExpensify commented on Nov 28, 2023

    @stitesExpensify
    Contributor

    Closing this for now since we haven't heard anything for a while

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions