[HOLD for payment 2023-06-30] [HOLD for payment 2023-02-17] `Test Preferences section` disappear when the android app is reloaded in offline mode

[kavimuru]

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

---

Actions Performed:

1. Go to Settings > Preferences
2. Toggle on Use Staging Server
3. Turn off the internet
4. Kill the app
5. Open the app again
6. Turn on the internet
7. Go to Settings > Preferences

Expected Result:

Test Preferences are displayed

Actual Result:

Test Preferences are not displayed until the app is reloaded

Workaround:

unknown

Platforms:

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

• Android / native

Version Number: v1.2.49-0
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

23-01-05-11-57-49.mp4

az_recorder_20230105_194050.2.mp4

Expensify/Expensify Issue URL:
Issue reported by: @adeel0202
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1672903057105979

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01cb1e08ff6673c342
• Upwork Job ID: 1618076485127200768
• Last Price Increase: 2023-01-25

[luacmartins]

I can work on this

[luacmartins]

I'll take a look at this today!

[luacmartins]

Got caught up with the deploy and the mobile fire. I'll get to this tomorrow!

[greg-schroeder]

Bug0 Triage Checklist

Note: see this SO for more information.

• The "bug" is actually a bug
• The bug is not a duplicate report of an existing GH.
  • If it is, close the GH and add any novel details to the original GH instead
• The bug is reproducible, following the reproduction steps.
  • If the GH doesn’t have steps to reliably reproduce the bug and you figure it out, then please add them.
  • If you’re unable to reproduce the bug, add the Needs reproduction label.
  • Comment on the issue outlining the steps you took to try to reproduce the bug, your results and tag the issue reporter and the Applause QA member who created the issue. Ask them to clarify reproduction steps and/or to check the reproduction steps again. Close issue.
• The GH template is filled out as fully as possible
  • The GH body and title are clear (ie. could an external contributor understand it and work on it?)
• The GH was created by an Expensify employee or a QA tester
• If the bug is an OldDot issue, you should decide whether it is widespread enough to justify fixing or it is better to wait for reunification. If it’s better to wait, close the GH & provide this justification
• If there's a link to Slack, check the discussion to see if we decided not to fix it
• Decide if the GH should be resolved by an External contributor or Internal engineer, add the appropriate label

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01cb1e08ff6673c342

[greg-schroeder]

Marking this as Internal accordingly