Desktop - LHN is not displayed when reopening app from dock

[isagoico]

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:

There's currently no solid reproduction steps:

1. Leave the desktop app minimized for a little while
2. Open the app.

Expected Result:

LHN and UI is displayed without visual issues.

Actual Result:

LHN is missing from the sidebar

Workaround:

Unknown.

Platform:

Where is this issue occurring?

• Desktop App

Version Number: 1.1.8-0

Reproducible in staging?: Yes
Reproducible in production?: Unknown

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

Notes/Photos/Videos: Any additional supporting documentation

Note: @parasharrajat was also able to reproduce this one.

Expensify/Expensify Issue URL:

Issue reported by: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1634705195483300

View all open jobs on GitHub

[MelvinBot]

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

[deetergp]

Don't think this will touch the back end at all so it should be fine for an external contractor to work on.

[MelvinBot]

Triggered auto assignment to @marklouisdeshaun (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[MelvinBot]

Triggered auto assignment to @stephanieelliott (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[deetergp]

I re-applied the External label since I read earlier in the day that @marklouisdeshaun was leaving the CM team.

[parasharrajat]

We don't need to export this yet. There are no reliable steps. This was a one-time thing for me and I am making a major change to the drawer #5745 and thus I am sure this issue will become invalid.

[deetergp]

Thanks for the update @parasharrajat! I've removed the label (again) for the time being. If you feel that your fix has resolved this issue feel free to close this one.

[parasharrajat]

Great. I will tag that in the PR.

[deetergp]

Thanks, Rajat!

[roryabraham]

@isagoico Can you confirm this issue will be tested as part of the weekly KI retests?

[isagoico]

@roryabraham We currently don't test issues raised in the #expensify-open-source so this was not going to be included in the list, but we can definitely add this one (or others) to the KI Retests. CC @mvtglobally

[roryabraham]

Hmmm I thought that E/App issues went through weekly KI retests along with E/E issues

[isagoico]

All E/App issues (raised by Applause testers) are going through weekly KI. What I meant before is that issues raised on the #expensify-open-source don't go through the KI Retests at the moment and we could add them to the KI retests round if requested on the issue (similar like what you did here

[roryabraham]

Okay, well for now let's just add this one to KI retests if possible! Thanks!

[mvtglobally]

Issue not reproducible during KI retests. (First Week)

[mvtglobally]

Issue not reproducible during KI retests. (Second Week)

[stephanieelliott]

Holding while we wait on reproduction

[mvtglobally]

Issue not reproducible during KI retests. (Third Week)
@roryabraham Let us know if we should close it or keep checking

[mvtglobally]

Issue not reproducible during KI retests. (Fourth Week)

[stephanieelliott]

Still waiting on reproduction. IMO I think we can stop testing this since it's unreproducible 4w in a row. Will wait for @roryabraham to weigh in to make the final call though!

[roryabraham]

I think the standard time to close KI's is 6 weeks, right @mvtglobally?

[isagoico]

Nope, the standard is 3 weeks of no reproduction and then close.

[roryabraham]

Oh, then ya let's close this out.