"User Profiling" Toggle Not Working

[IuliiaHerets]

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

---

Version Number: v9.0.17-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): abebemiherat@gmail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Sign in to the new dot.
2. Click on Ctrl + D.
3. Observe that the modal appears.
4. Attempt to toggle the 'User Profile' and notice that it does not work.

Expected Result:

The user should be able to toggle the 'User Profile'.

Actual Result:

The user is unable to toggle the 'User Profile'.

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Bug6563790_1722977273083.Screen_Recording_2024-08-06_at_1.05.53_PM.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @zanyrenney (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.

[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

[marcaaron]

The user should be able to toggle the 'User Profile'.

Sorry, did you mean Use Profiling ?

Gonna remove the blocker here. This is an internal tool and not mission critical.

[IuliiaHerets]

@marcaaron Yes, Use Profiling, sorry for confusing

[Tony-MK]

This is issue doesn't actually occur on the main branch

[zanyrenney]

can reproduce on staging

[zanyrenney]

but i agree this is not critical

[zanyrenney]

do we actually do this? @thienlnam I see only one ever mention of "user profiling" in slack and its in reference to iOS:

[zanyrenney]

asking here https://expensify.slack.com/archives/C05LX9D6E07/p1723039606440559

[kirillzyusko]

It happens because "hosting" is not allowing "self-profiling":

Document policy violation: js-profiling is not allowed in this document.

I described it here: https://github.com/margelo/react-native-release-profiler?tab=readme-ov-file#web-support

We enabled this toggle in dev mode, but to enable it in prod (staging and prod) you'll need to add 'Document-Policy': 'js-profiling' header to html response.

I don't have permissions to deploy so I can not fix it, but if someone can shed some light on where and how the app is hosted (is it AWS S3?) then I can co-operate with that person and together we can fix that 🤞

[zanyrenney]

Hey @thienlnam any progress here please? I see you added the Infra label - what's the intention for that to assign a specific person/group so that we can move this forward or are you still able to manage it?

[thienlnam]

Bumped this back to a weekly since it's not high priority.

I need to double check where we want to add this header - chances are it will probably be in our salt config

[thienlnam]

Nice, resolved! We only added this to staging and adhoc builds