Personal Details - Data does NOT show after a few seconds with HT expensifail account

[kbecciv]

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

---

Found when executing PR #17944

Action Performed:

1. Open the app and logout if you're currently logged in
2. Log in with HT expensifail account
3. Disable network
4. Open Settings > Profile > Personal Details
5. Observe that data (Legal name, Date of birth, Home address) isn't showing yet
6. Enable network
7. Verify that data shows after a few seconds

Expected Result:

Data shows after a few seconds with HT expensifail account

Actual Result:

Data does NOT show after a few seconds with HT expensifail account

Workaround:

Unknown

Platforms:

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

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

Version Number: 1.3.6.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Bug6033187_Recording__2592.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~018af1590591eb5887
• Upwork Job ID: 1661464526132850688
• Last Price Increase: 2023-05-24

[MelvinBot]

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[jasperhuangg]

TLDR: With the parallel Pusher stuff that's being worked on right now this problem should go away eventually, closing

I wasn't able to reproduce this bug on my account. After looking at the Network Tab in the OP, the requests for the HT account were just too slow. This was evidenced by how it took an abnormally long amount of time to sign in. But it isn't caused by an explicit bug in our code.

This isn't as much of an issue with the personal details as much as it is an issue with our API being slow for requests that send a ton of Pusher notifications. With the parallel Pusher stuff that's being worked on right now this problem should go away.

[kbecciv]

@jasperhuangg Did you use HT account?
I'm able to reproduce the issue with mine HT account, please attache the video with speed test as well. My understanding that PR is fixed for regular (simple) users, but NOT for High Traffic Accounts.

Recording.2600.mp4

[anmurali]

TLDR: With the parallel Pusher stuff that's being worked on right now this problem should go away eventually, closing

@jasperhuangg is this still true? If yes, we can close this yea?

[jasperhuangg]

@anmurali
Ionatan's parallel pusher stuff https://github.com/Expensify/Web-Expensify/pull/37120 should be deployed to staging pretty soon (it's already been merged to main). Let's just keep this open for now and leave it as is (Needs Repro). Once that PR gets deployed to staging let's ask @kbecciv to test again. My theory is that it should go away once that PR goes out.