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

[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

[OSBotify]

👋 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.

[melvin-bot]

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

[conorpendergrast]

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

[0xmiroslav]

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

[amyevans]

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!