Profile - When opening profile, in settings, "Private" section loads infinitely.

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.38-0
Reproducible in staging?: Y
Reproducible in production?: N
Issue reported by: Applause Internal Team

Action Performed:

1. Open the staging.new.expensify.com website.
2. Navigate to settings.
3. Tap on "Profile"
4. Scroll down to "Private"
5. Verifiy the section loads smoothly and the user can access all the fields in the category.

Expected Result:

All the sections in profile, should load properly and the user should be able to access to all the available fields.

Actual Result:

The "Private" section in profile settings, loads infinitely and the user is not able to see any of the fields in the section. Despite refreshing the page or logging out and in again, the infinite loading keeps displaying.

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6608779_1726744529738.Infinite.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @dangrous (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

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

[IuliiaHerets]

We think that this bug might be related to #wave-collect - Release 1

[grgia]

Likely caused by #48517 @rushatgabhane

[dangrous]

I think we can close this one out, no payment necessary.